S02 - s/environmental variables/environment variables/g please

[Randal L. Schwartz]

Please, let us agree to use the traditional name of "environment variables" in
the docs, and not re-introduce its bastardized cousin, which hurts my ears.
Thanks.

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<mer...@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

[ja...@mastros.biz]

On Sat, Apr 29, 2006 at 07:50:02AM -0700, Randal L. Schwartz wrote:
> Please, let us agree to use the traditional name of "environment variables" in
> the docs, and not re-introduce its bastardized cousin, which hurts my ears.
> Thanks.

I think they are different things. An "environment variable" is something
in %*ENV. An "environmental variable" is a variable which was declared with
env $foo, and which can be seen by callers.

I rather dislike this naming scheme, but can't think of a better one.

-=- James Mastros

[Randal L. Schwartz]

>>>>> "james" == james <ja...@mastros.biz> writes:

james> I think they are different things. An "environment variable" is
james> something in %*ENV. An "environmental variable" is a variable which
james> was declared with env $foo, and which can be seen by callers.

If they both have "env"-ish stuff in the name, let's use the same
name for both. If they are far enough apart that they should be
distinct, call them something different.

But to have %*ENV be called "environment variables" while "env $foo" be called
"environmental variables", you're cruisin' for a world of hurt, and I say this
as someone who will have to document this and teach this to a group of newbies
for every week of my upcoming life.