Comments on: Dehydra progress http://blog.mozilla.com/tglek/2008/01/25/dehydra-progress/ Just another Blog.mozilla.com weblog Sun, 12 Feb 2012 07:38:09 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Boris http://blog.mozilla.com/tglek/2008/01/25/dehydra-progress/comment-page-1/#comment-13121 Boris Sat, 23 Feb 2008 22:52:34 +0000 http://blog.mozilla.com/tglek/2008/01/25/dehydra-progress/#comment-13121 > Given how easy life is with plugins I am amazed that people chose to go uphill bothways and not collaborate on a plugin interface for their crazy GCC extensions Unfortunately, plugins accessing compiler internals have always been frowned upon by many regulars of the gcc community and more importantly by the Steering Commitee, it is only since just very recently that first steps are being taken -and in fact allowed to be taken- to implement the necessary infrastructure mechanisms within gcc. But there are still many non-technical issues that people are afraid of, mainly related due to concerns about possible ways to circumvent the GPL . If you are interested in details, you may want to search the gcc archives for the terms "introspector", "plugins", "scripting", "intermediate state" Boris > Given how easy life is with plugins I am amazed that people chose to go uphill bothways and not collaborate on a plugin interface for their crazy GCC extensions

Unfortunately, plugins accessing compiler internals have always been frowned upon by many regulars of the gcc community and more importantly by the Steering Commitee, it is only since just very recently that first steps are being taken -and in fact allowed to be taken- to implement the necessary infrastructure mechanisms within gcc.
But there are still many non-technical issues that people are afraid of, mainly related due to concerns about possible ways to circumvent the GPL .

If you are interested in details, you may want to search the gcc archives for the terms “introspector”, “plugins”, “scripting”, “intermediate state”

Boris

]]> By: tmielczarek http://blog.mozilla.com/tglek/2008/01/25/dehydra-progress/comment-page-1/#comment-10938 tmielczarek Sun, 27 Jan 2008 17:44:47 +0000 http://blog.mozilla.com/tglek/2008/01/25/dehydra-progress/#comment-10938 This is awesome. I hope more projects that involve parsing C++ go this route. I just spent a few days fighting SWIG because its C++ parser isn't quite perfect. It's frustrating, but hopefully things will continue to evolve now that GCC plugins are an option for people. This is awesome. I hope more projects that involve parsing C++ go this route. I just spent a few days fighting SWIG because its C++ parser isn’t quite perfect. It’s frustrating, but hopefully things will continue to evolve now that GCC plugins are an option for people.

]]> By: Brendan Eich http://blog.mozilla.com/tglek/2008/01/25/dehydra-progress/comment-page-1/#comment-10905 Brendan Eich Sun, 27 Jan 2008 00:16:56 +0000 http://blog.mozilla.com/tglek/2008/01/25/dehydra-progress/#comment-10905 ... will remain in the ActionMonkey future, I mean (when SpiderMonkey and Tamarin [tamarin-tracing, of course] finish their slow mating dance). /be … will remain in the ActionMonkey future, I mean (when SpiderMonkey and Tamarin [tamarin-tracing, of course] finish their slow mating dance).

/be

]]> By: Brendan Eich http://blog.mozilla.com/tglek/2008/01/25/dehydra-progress/comment-page-1/#comment-10904 Brendan Eich Sun, 27 Jan 2008 00:15:44 +0000 http://blog.mozilla.com/tglek/2008/01/25/dehydra-progress/#comment-10904 You won't have to switch DeHydra to Tamarin -- the "jsapi.h" JS API (mostly; I'll check the entry points used by DeHydra but IIRC they're likley to stay) will remain. /be You won’t have to switch DeHydra to Tamarin — the “jsapi.h” JS API (mostly; I’ll check the entry points used by DeHydra but IIRC they’re likley to stay) will remain.

/be

]]>