On Thu, Jul 8, 2010 at 8:19 AM, Lukas Renggli <renggli@gmail.com> wrote:
Use a pragma to mark class pragmas. Or simply know which pragma
selectors need to be interpreted on the class.

[I know Lukas knows this but I'll say it anyway].

Do the former. The latter is weak. �It means two unrelated packages wanting to add a class pragma end up colliding. �Using a pragma to mark the class pragma allows choosing an arbitrary selector and hence makes it easy to avoid the collision.
�

Lukas

On Thursday, July 8, 2010, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
> May be using a class method?
> But yes this would be important.
>
> Alex if we use comment we would have to parse them and this is not good.
>
> Stef
>
> On Jul 8, 2010, at 3:35 PM, Torsten Bergmann wrote:
>
>> Hi,
>>
>> while it is possible to annotate methods using Pragmas,
>> what about classes?
>>
>> Thx
>> T.
>> --
>> GRATIS f�r alle GMX-Mitglieder: Die maxdome Movie-FLAT!
>> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

--
Lukas Renggli
www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project