[squeak-dev] Re: <Method Tags> (Pragmas)

Hannes Hirzel hannes.hirzel at gmail.com
Fri Apr 30 09:09:33 UTC 2010

The name method tag makes a lot of sense.

An example:
If I have a method tagged with <systemsetting> I know how I can
collect together all the settings in the whole image. No need for
'registering' ......

And the tag <primitive: ...> marks methods which have implementations
in the virtual machine.

A tag like <menu> marks methods which should be called from the menu.
Another <menu> tag tells the system which label to use and maybe
another  one which menu  (something like this.... needs elaboration,
this is an on-going discussion)


On 4/30/10, Hannes Hirzel <hannes.hirzel at gmail.com> wrote:
> On 4/30/10, Bert Freudenberg <bert at freudenbergs.de> wrote:
>> On 30.04.2010, at 05:23, Andreas Raab wrote:
>>> On 4/29/2010 1:23 PM, Travis Griggs wrote:
>>>> 2) I push, at ever juncture I can, the term <tagged methods> and
>>>> <method
>>>> tags>. The <tag> term grew on me for a set of reasons.
>>> I think that's a great term. It doesn't have the compiler connotations
>>> of
>>> "pragma", is shorter than "annotation" yet very concise and flexible. I
>>> like the sound of, e.g., "the apicall tag instructs the compiler to
>>> generate the code for some FFI call", "the preference tag allows
>>> discovery
>>> of preferences", the "type tag can be used to annotate variables". It
>>> really works for me.
>>> In fact, I raise my hand and vote for renaming Pragma to MethodTag :-)
>> +1
>> Thanks Travis!
>> - Bert -
> +1
> --Hannes

More information about the Squeak-dev mailing list