At first sight, I prefer the hooks approach. Not just cos I'm a noob
(although that is a compelling reason in itself) but also because it
happens during the main compile. A separate innovation could have
different flags so it wouldn't be authoritative anymore.
But it absolutely has to follow the p
Well it seems to be able to report a lot of syntax errors even if
they're close together, so it must be getting back on its feet fairly
quickly. I don't know how that works. Maybe it just scoots along to
the next semicolon or maybe you explicitly have productions like "if
(syntax error) { ... }".
Hi All,
I have this brainstorm which I'd like to get some feedback on.
I reckon it's a bad idea to make source browsing info with a separate
program like cscope or etags. I reckon it's the compiler's job.
Why? (1) Because only the compiler can do it authoritatively, after
all, it decides what's
