Comments on: GCC + SpiderMonkey = GCC Dehydra http://blog.mozilla.com/tglek/2008/01/17/gcc-spidermonkey-gcc-dehydra/ Just another Blog.mozilla.com weblog Sun, 12 Feb 2012 07:38:09 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Tom Tromey http://blog.mozilla.com/tglek/2008/01/17/gcc-spidermonkey-gcc-dehydra/comment-page-1/#comment-10547 Tom Tromey Sat, 19 Jan 2008 00:07:39 +0000 http://blog.mozilla.com/tglek/2008/01/17/gcc-spidermonkey-gcc-dehydra/#comment-10547 I'm really happy to hear that this is working. I think this is an important direction for GCC to go, and GCC needs someone to drive it a bit... As to your points: for #1, I agree completely and I already know how to fix this for C. For #2, I'm not so sure. I saw some problems here with the column number work, but it isn't clear that this would be any better with a generated parser. Can you get end-of-node information by looking at all the sub-nodes? I suppose spelling of numbers, and parens, get in the way here. More stuff to do :-) #3 is definitely a problem, and kind of a pain internally too. I'm sure it is fixable but I'd imagine it is a lot of work. On politics, unfortunately you are right :(. There's some hope we can get forward motion here, though. I’m really happy to hear that this is working. I think this is an important direction for GCC to go, and GCC needs someone to drive it a bit…

As to your points: for #1, I agree completely and I already know how to fix this for C.

For #2, I’m not so sure. I saw some problems here with the column number work, but it isn’t clear that this would be any better with a generated parser. Can you get end-of-node information by looking at all the sub-nodes? I suppose spelling of numbers, and parens, get in the way here. More stuff to do :-)

#3 is definitely a problem, and kind of a pain internally too. I’m sure it is fixable but I’d imagine it is a lot of work.

On politics, unfortunately you are right :( . There’s some hope we can get forward motion here, though.

]]>