From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-01-16 03:23:00
David Abrahams wrote:
> "Felix E. Klee" <felix.klee.jamboost_at_[hidden]> writes:
>>exe hello : hello.cpp : <qt>on ;
>>Of course, I see that it might be problematic for Jam to decide which header
>>files need to be moc'ed and which ones are "external" (after all one doesn't
>>want to moc the standard QT include files).
> Can't we use a different extension for these? They aren't standard
> C++ after all...
They are! Those header files are processed by ordinary C++ compiler. The trick
is that QT's special things, (Q_OBJECT, slots, signals) are #defined to be empty.
Anyway, we can use special suffix for those files. There's still a problem
with renaming them if you add/remove the Q_OBJECT macro call.
> We ought to have a way to explicitly declare the type of a file,
> overriding its extension.
That's completely true. For example, one of my potential use cases requires
that you specify a list of C++ sources, and then say that this and that source
file must be specially processed. I've just filed
(Persons without Scarab account can logic with username "anonymous" and the
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk