On Fri, Feb 6, 2015 at 5:58 PM, Thierry Goubier <thierry.goubier@gmail.com> wrote:1- expressing a link to some metadata used by low level tools: compiler, C lang generator, etc... primitives for me are part of that. Kind of neat to see that unified.I see pragmas used mainly for two things:Hi Eliot,maybe I'll frame the core question a bit differently, thanks to your explanations.btw, I just used a pragma to solve this issue of getting correct debugger behaviour for halting and stepping over #halt statements [1].� There seem about a dozen methods that can cause a #halt spread between Object and Halt classes which should all behave similarly, so the options would seem* hardcode all these methods either into to check for in Halt>>signalerContext (or into a helper method called from #singalerContext)* have a convention for a certain protocol to hold these methods, which Halt>>signalerContext can look up (except currently the methods on Object are an extension protocol)* tag each such method with a pragma.� This simplified the solution a lot.� The search of the call stack just asked each method if it had the <debuggerCompleteToSender> pragma.
�I think discoverability is an issue with pragmas.� From Nautilus you can't "see" which methods contain which pragmas.� I wonder if one solution for this would be for pramga methods to be grouped under a <virtual-protocol> in the third pane of Nautilus.