On Tue, Sep 15, 2009 at 05:17:29PM +0200, Hans-Peter Diettrich wrote: > >> Then you don't want to use any of the many C libraries, out there? Like > >> lex, yacc, regexp, zip, SVN... > > > > We can already statically link to C code, so what exactly is the point? > > True, header converting is pain, but a blessing compared with the amount of > > work to maintain a fullblown C compiler. > > What extra work do you mean? > > A compiler front-end translates the source code into an internal format, > from which the back-end generates the executable code.
The frontend, and making sure the generated code meets targets, survives testsuites, complies to standard (e.g. aliassing rules) > > Moreover it would be a feeble shade of a compiler to compile a handful of > > libs only, and you get tons of maintenance work in return. All the C parsing > > and implementation oddities, GCC compatibility issues, tools preparation > > ( autoconf etc), libraries etc. > > The ToPas C preprocessor and parser has been tested for MSVC and gcc > compatibility. Parsing compatibility I assume. So it eats everything that could turn up in a gcc header? It eats the entire /usr/include on Linux? -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus