Subject: Re: Option to make cpp(1) not accept named pipes or devices as
To: Hubert Feyrer <hubert@feyrer.de>
From: Jim Wise <jwise@draga.com>
List: tech-toolchain
Date: 11/29/2004 16:50:46
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 29 Nov 2004, Hubert Feyrer wrote:
> On Mon, 29 Nov 2004, Jim Wise wrote:
>> Any suggested improvements before I do so?
>
> Add a command line switch? It's the unix way of altering command behaviour...
Eh? From $PATH to $EDITOR to $TERM, lot's of programs alter their
behavior based on environment variables.
More specifically, I'm somewhat hesitant to use a flag in this case.
My main concern is that this will be most often used by programs
exec'ing cpp, and not all of them will be smart about allowing arguments
to be part of ${CPP}, so an environment variable provides a saner way to
modify cpp's behavior when called from an already-existing binary or
script.
There's also the concern that if users decide to use a non-basesrc cpp
(as _many_ users do via pkgsrc/lang/gcc34), a new command line option
will cause cpp to fail outright, while a new environment variable will
not.
That's why I chose the route I did, anyway...
- --
Jim Wise
jwise@draga.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)
iD8DBQFBq5m5pRpI6SYACmIRAvvpAKCckuS6X09gPsu8Zm8+SjfFvTnvFwCfV9AX
O1At1SiqhiREYQKrxoYorzw=
=/AGj
-----END PGP SIGNATURE-----