Now the first problem is that #package is used by RPackage so
redefining it on Class breaks the system. #package: might be less
problematic but… for now I will switch back to #category:

I was thinking SomeClass < #NameOfNewClass should return a builder
object, but in that case there is no way for the builder to know when
the cascade is finished; it can of course do things on the fly, but
that implies recompiling the class for each message… not really
beautiful.

Now the first problem is that #package is used by RPackage so
redefining it on Class breaks the system. #package: might be less
problematic but… for now I will switch back to #category:

I was thinking SomeClass < #NameOfNewClass should return a builder
object, but in that case there is no way for the builder to know when
the cascade is finished; it can of course do things on the fly, but
that implies recompiling the class for each message… not really
beautiful.

Suggestions?

we can also fix that the package message should be always sent as the latest one by convention.

Re: Class declaration syntax

On Dec 15, 2011, at 3:36 PM, Damien Pollet wrote:
>
>
> I was thinking SomeClass < #NameOfNewClass should return a builder
> object, but in that case there is no way for the builder to know when
> the cascade is finished; it can of course do things on the fly, but
> that implies recompiling the class for each message… not really
> beautiful.
>
> Suggestions?

I think Alex has a point: just don't use cascades. Add all the needed methods.
(this forces people to keep the order, too).

Re: Class declaration syntax

> Hi all,
>
> back to Coral after a (much too long) teaching hiatus, I'm pondering
> what the best solution is for the class declaration syntax.
>
> The usual message will always work, of course:
>
> SomeClass subclass: #NameOfNewClass
> instanceVariableNames: 'a b c'
> classVariableNames: 'D E F'
> poolDictionaries: ''
> category: 'Foo'
>
> But one idea of the prototype was to make that a bit more flexible and
> terse, by using a cascade:
>
> SomeClass < #NameOfNewClass
> iv: 'a b c';
> shared: 'D E F';
> package: 'Foo'
>
> Now the first problem is that #package is used by RPackage so
> redefining it on Class breaks the system. #package: might be less
> problematic but… for now I will switch back to #category:
>
> I was thinking SomeClass < #NameOfNewClass should return a builder
> object, but in that case there is no way for the builder to know when
> the cascade is finished; it can of course do things on the fly, but
> that implies recompiling the class for each message… not really
> beautiful.
>
> Suggestions?
>
> --
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet>
> _______________________________________________
> Pharo-coral mailing list
> [hidden email]> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-coral