2017-11-09 22:03 GMT+01:00 Stephane Ducasse <stepharo.self@gmail.com>:
>>
>
> Then should not we replace STON based class definition with actual smalltalk
> based definition? Tonel could parse class definition in similar way like it
> parses methods.

Probably not :) but one of this day we will change the class
definition in Pharo adn we do not really want to impact tonel.
For me tonel is a storage format and it is ok like that.
Using Strings will solve the glitches.

Stef

But why accepting to depend on syntax of method body?
Especially in a language where you can define parserClass/compilerClass?

Maybe it would have possible to prepend each line with a space at write time, and allways put end delimitor in first column / separated lines
[
�������� ^self
]
Then at read time, just scan line by line, remove first space if present, stop when first column is ].
It's not super nice if you have string literals spanning multiple lines, but it's syntax agnostic and futureproof, while still human readable/writeable.