dmitry boyarintsev schrieb: > On Fri, May 28, 2010 at 11:06 PM, Adem <[email protected]> wrote: >> Would I have your blessing if I proposed a bounty to unentwine them so that >> each one of those major modules becomes objects in tehir own right >> --commnicating with one another through public/published events and >> properties. >> >> I can guess that it would be hard to do, but I feel it will be absolutely >> impossible without your (and the rest of compiler team's) blessing. > > I can see another benefit of separating parser/tokenizer from code > generation.
Separating code generation is easy. The bigger problem is the symtable information: fpc uses symbol information while parsing and generating the parse tree for better error checking and for simpler and faster parsing. Further, the compiler is a really complex piece of software so we don't want to be hindered by exposing functionally too much, this would make the oil tanker a continent. BTW: We had this discussion ten years ago already when fpdoc was made and it was decided to write a separate parser after failed attempts to use fpc's frontend. > Is easier and better support of newer targets. I'm talking > about long wished LLVM, and even possibly Java and/or .NET. (No need > to support all possible features, but generate their native > byte-code). > So far, the internal structure of the compiler is the **only** > obstacle (caused by lack of manpower, actually) > > thanks, > dmitry > > -- > _______________________________________________ > Lazarus mailing list > [email protected] > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus > -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
