Re: Re: software design clarification

On 5/8/07, Stefan Seefeld <[email protected]> wrote:
> GCC-the-platform ships its own system headers (and libraries), and thus
> is very sensitive about the target platform.

1. GCC is a huge project - installation procedure is not simple
2. "own system headers" - user wants AST builder to create the tree
from actually used headers

> On the other hand, GCC-the-compiler is quite a bit more flexible. I
> don't think it would be such a huge effort to make it accept some MSVC-
> specific constructs.

It is a huge. This is one of the reasons GCCXML is not going to be
upgraded any time soon.

> Also, the emulation code in Synopsis merely simulates native compilers
> by providing predefined macros and include search paths so its own preprocessor
> can be used with system headers (from the emulated compiler). A similar
> approach could work for GCC, too. It's just a matter of some programming. :-)

"some programming" :-)))). I took a look on files that parse and
analyze C++ code: they have huuuuuuuuuuge size.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/