This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Defining a common plugin machinery
- From: "Diego Novillo" <dnovillo at google dot com>
- To: "Hugh Leather" <hughleat at hotmail dot com>
- Cc: "Grigori Fursin" <grigori dot fursin at inria dot fr>, "Brendon Costa" <bcosta at avdat dot com dot au>, "Taras Glek" <tglek at mozilla dot com>, "Basile STARYNKEVITCH" <basile at starynkevitch dot net>, gcc at gcc dot gnu dot org, "Sean Callanan" <spyffe at cs dot sunysb dot edu>, "Cupertino Miranda" <cupertino dot miranda at inria dot fr>, clattner at apple dot com, iant at google dot com, "Taras Glek" <taras dot judge at shaw dot ca>, "Mike O'Boyle" <mob at inf dot ed dot ac dot uk>
- Date: Thu, 9 Oct 2008 06:26:35 -0700
- Subject: Re: Defining a common plugin machinery
- References: <48CF93F7.8010901@google.com> <48E45457.2090408@starynkevitch.net> <48E461CA.9030808@avdat.com.au> <48E46A64.9060406@starynkevitch.net> <48EA89AB.6080707@mozilla.com> <48eda3c7.0405560a.7aa9.1031@mx.google.com> <48EDA48E.6060004@mozilla.com> <48EDA5D7.2050305@avdat.com.au> <48eda87d.0437560a.43f7.11c2@mx.google.com> <BLU142-DAV8F41EC60D9554F88946FAC13A0@phx.gbl>
On Thu, Oct 9, 2008 at 05:26, Hugh Leather <hughleat@hotmail.com> wrote:
> I think the env var solution is easier for people to use and immediately
> understand. There would be nothing to stop those people who don't like env
> vars from using the shell wrapper approach. Why not allow both?
Environment variables have hidden side-effects that are often hard to
debug. It is easy to forget that you set them. I also agree that we
should not allow environment variables to control plugins.
Diego.