Re: [Axiom-developer] ENV

[Gabriel Dos Reis]

root <address@hidden> writes:

| > No, again you're making the assumption that ENV does not mean anything
| > particular.  ENV means something very precise is POSIXilly correct
| > shells.  In particular its value is exported, which means that if you
| > don't set it, you get what it is supposed to be (not empty).  The
| > above is an experiment you can reproduce with a POSIX-compliant shell.
| > 
| > The issue is very simple: avoid ENV.  Use MAKEFLAGS (which I'm working on).
| 
| Eh? I have no idea what you're talking about.

That I've figured out :-)

| It is perfectly legal
| to set and reference shell variables and this "prefix" technique
| is supported as standard syntax by shells.

Nobody claims that is illegal.  We are talking of a *specific variable*
here, that happens to have a *specific meaning* for shells.

[...]

| One example of the shell variable (mis)use in Axiom is the handling
| of the PLATFORM variable. This variable is passed on the command line
| to certain C calls in a define as in -D${PLATFORM}

Oh, let's talk about that hack another day -- I have enough for today.

[...]

| So the point is that there are a lot of variables collected into
| ENV and they have a lot of different uses and abuses. 

You have completely missed the point.

-- Gaby