(oops, sorry, hit "reply" instead of "reply to all", trying again) On 3/1/06, Julian Scheid <julian@xxxxxxxxxxx> wrote: > What I'd really like to do is completely replace the parser with a new > one written from scratch (preferrably, a generated one.) In addition, > the parsing and type resolution steps should be cleanly separated - they > are somewhat intermingled at the time. What are the odds of replacing it by calls into ecj's parsing engine, since that's already pretty mature and implemented in pure Java? The licensing problems that may exist at this time seem to be resolvable, as evidenced by the plan to use ecj as gcc's Java frontend in the future... Stuart. -- http://sab39.dev.netreach.com/ -- http://sab39.dev.netreach.com/
