>>>>> "LW" == Larry Wall <[EMAIL PROTECTED]> writes:
LW> On Wed, Jul 27, 2005 at 04:27:15PM -0400, Uri Guttman wrote:
LW> : then why not name it something like *?ENV (not to be confused with the
LW> : shell/exec env which is still %ENV i assume)?
LW> Of course, the fact that you have to say "not to be confused with"
LW> can be taken as indicating that people will in fact confuse them...
you could do it even worse by making the shell env be a method/entry of
the perl env (bad syntax ahead):
*?ENV.ENV<<PATH>>
but my original point stands in that all this is should be under one
builtin and it shouldn't be OS or VM. those should be parts of it and
maybe shell env should be part of it too. this thingy should encompass
all about this perl and the world it is in and the shell env is part of
that.
so other choices are the common and lame INFO and CONF. too bad ENV was
taken already. i wish we could invent new words. :)
bad idea: call it *?WALL cause everything is hanging on the wall.
uri
--
Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
