Could we have a list of the official pragmas because it starts to be a MESS!
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. Stef
On Wed, Oct 2, 2013 at 11:34 AM, Stéphane Ducasse <stephane.ducasse@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. HTH, Eliot
+100 Miguel Le 03/10/2013 01:44, Eliot Miranda a écrit :
On Wed, Oct 2, 2013 at 11:34 AM, Stéphane Ducasse <stephane.ducasse@inria.fr <mailto:stephane.ducasse@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.
HTH, Eliot
Then for smart suggestions, pragma AST nodes should have an 'implementorsOf' and 'references' commands on them :) Thierry Le 03/10/2013 01:44, Eliot Miranda a écrit :
On Wed, Oct 2, 2013 at 11:34 AM, Stéphane Ducasse <stephane.ducasse@inria.fr <mailto:stephane.ducasse@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.
HTH, Eliot
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
On Oct 3, 2013, at 1:44 AM, Eliot Miranda <eliot.miranda@gmail.com> wrote:
On Wed, Oct 2, 2013 at 11:34 AM, Stéphane Ducasse <stephane.ducasse@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
The finder has a "Pragmas" category :) Ben On Oct 3, 2013, at 1:44 AM, Eliot Miranda <eliot.miranda@gmail.com> wrote:
On Wed, Oct 2, 2013 at 11:34 AM, Stéphane Ducasse <stephane.ducasse@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.
HTH, Eliot
participants (5)
-
Benjamin -
Eliot Miranda -
Goubier Thierry -
Miguel Moquillon -
Stéphane Ducasse