CGAL users discussion list

[Zohar <>]

Actually the parsing should be the tough part, and my solution was no way a
bullet proof, but for the first version or proof of concept, I could make
some assumptions on the code, to make my life more easier. The user for
example could choose with a pragma to bypass the smart makefile. 
I wasn't aware of Boost.Wave, so thanks for the tip.

My method might be time consuming as you say, or move the overload to the
linker, but still the fact remains that if I manually divide my .cpp, things
go faster, and I have the feeling that running a basic parser wouldn't short
by much the advantage of a smart makefile.

I'll might try comp.lang.c++.moderated, although at first glance they sound
too formal and restrictive for a casual posting.

Thanks Philipp.

--
View this message in context: 
http://cgal-discuss.949826.n4.nabble.com/Smart-makefile-for-C-at-function-level-tp3895883p3903623.html
Sent from the cgal-discuss mailing list archive at Nabble.com.