Re: [Ctool-develop] suggestions to provide a 'real' public API

[Stefan S. <se...@sy...>]

Stefan Seefeld wrote:

> * the parsing should be separate from preprocessing, such that
>   users can plug in their own preprocessors.

right now the project.cpp file contains definitions used to call
the preprocessor. It's the 'Project::parse' method that uses
these settings, if the 'cpp_cmd' argument is NULL. Is that really
a good idea ? I'd suggest we require this argument to be something
non-zero, so the caller of Project::parse has to care for the preprocessor
that is to be called. That way we could remove lots of macros and
defines from the src/ build instructions, and only the frontend (i.e.
the 'Project::parse' caller) would be responsible for it.

What do you think ?

On a slightly different (but related) note: I'd really like to get the
tests up and running on my system before I make any important changes to
the actual code (as opposed to the build system infrastructure), such
that I can see immediately whether my changes incure regressions.
Unfortunately, the vast majority of the test don't pass.
Anything we can do about this situation ?

Regards,
		Stefan