>From memory one class of class/trait and one for extension
In class/Trait
"class / trait comments
comment"
Special STON order for classes to minimic our logical order (ie
package tag add the end).
Class {
}
or
Trait {
name: #T
}
+
Point class >> x: anInt1 y: anInt2
[
^ self new setX: anInt1 Y: anInt2
]
+
STON for meta data
{category : "printing"}
Since I do not know STON all the above can be wrong but this is the idea.
Stef
On Fri, Sep 8, 2017 at 10:02 PM, Eliot Miranda <eliot.mira...@gmail.com> wrote:
> Hi All,
>
>> On Sep 8, 2017, at 9:44 AM, Stephane Ducasse <stepharo.s...@gmail.com> wrote:
>>
>> Hi all
>>
>> At ESUG we discussed with Esteban, martin mcClure, Dale and (many many
>> others :), esteban designed a nice class file format. So that we will
>> not have 2Gb of space on harddisc, problems with long method names and
>> sluggish commits.
>
> Wow, that's great news! It'll make it much easier to import from Pharo hit
> repositories. Thank you, Esteban!
>
> Can someone post the grammar or a description of the syntax asap?
>
>>
>> He is waiting at Wien and is probably checking everything right now.
>>
>> It is a nice format because we will be able to use it to communicate
>> by emails using it. So readable, compact and I like it :)
>
> Lovely! Details please :-)
>
>>
>> Stef
>>
>
