On Tue, Jun 04, 2013 at 10:07:03PM +1000, mjch wrote:
> Wouldn't that make having /usr/bin/cpp in any set other than comp a little
> pointless?
>
If it depends on the compiler, as it is perfectly allowed, yes. This
only means that a cpp outside the comp set has to be standalone. But
this does not mean that a cpp provided in a binary tools set has to be
standalone.
POSIX stipulates that the portable call to the preprocessor is via the
compiler wrapper: c89 -E.
In the same league, a header is not mandatorily a file: it can be a
compiler artefact.
This is the way it is. I'm not saying anything else.
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
