[Pharo-dev] Could we have a list of the official pragmas because it starts to be a MESS!

Stéphane Ducasse stephane.ducasse at inria.fr
Thu Oct 3 03:42:09 EDT 2013

On Oct 3, 2013, at 1:44 AM, Eliot Miranda <eliot.miranda at gmail.com> wrote:

> On Wed, Oct 2, 2013 at 11:34 AM, Stéphane Ducasse <stephane.ducasse at inria.fr> wrote:
> For example
> <systemEventRegistration>
>         I have no idea (of course there is no comment) what is the use of this pragma.
> Chasing pragma interpreter can be painful so we should pay attention.
> Too many pragmas are a plague.
> Agreed.  Part of the design of pragmas is that, because they're message sends, they have implementations.  Those implementations can document what the pragma does.  The browser should include pragma selectors when doing "implementors..." so one can easily find the implementation of a pragma.  Also senders... should answer methods with pragmas with the selector being looked for.  If both of these are true then pragmas are much easier to explore and understand.

It does. But I want more :)
I want a comment that explain to me the purpose.
> HTH,
> Eliot

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131003/bb809d11/attachment-0002.html>

More information about the Pharo-dev mailing list