#$ENV{'CUSTOMENV'} = 'value';delete $ENV{CUSTOMENV}; -or- $ENV{PATH} = undef;
#<Alexander> what about unsetting them?
#<theorbtwo> same as any other hash: delete $ENV{CUSTOMENV}
#<Enlil> ummm... $ENV{PATH} = undef; or delete $ENV{PATH}; should work
#<Alexander> oh fantastic! ...are there any pros/cons to one or the other method of unsetting them?
#<Enlil> undef makes it undefined... delete removes completely from the hash.. so it no longer even exists... i would use delete..
#<Alexander> huh? "autovivify" -?!?
#Enlil notes that Alexander should look up exists, defined, and delete
#<theorbtwo> Also, look up ENV in perlvar.
#<Enlil> perldoc++++

#<Alexander> how do i do 1.00 + 1.00 = 2.00 instead of 1.00 + 1.00 = 2 and 1.00 + 1.50 = 2.50 instead of 1.00 + 1.50 = 2.5 --?
#<castaway> you just format the output with sprintf, alexander
#<castaway> (cos 2.50 == 2.5 )
#<Enlil> my $var = sprintf("%.2f",1.00 + 1.004); print $var;
#perl -le 'my $var = sprintf("%.2f",1.00 + 1.004); print $var;'

perl -le 'printf("%.2f",1.00+1.032);'
printf is like sprintf, except that it prints the formatted string, rather then returning it.
(You could say that the other way around, which is more historicly accurate, and makes the names make sense.)
Printf also ignores $\, as you've noticed; -l is of no help.
 happen to know why?
 I don't know. I suspect because it simply uses printf directly from C.
 nods.
 If there was, or is, a rationale for why it <em>should</em> be that way, I haven't heard it.
 i have seen the light and now understand the niftiness of the printf now. wow, perl -e 'printf("%.2f", 1 .00+1.032 .00+74);' equals 85.03!
 there is no shame spending an afternoon looking at [http://www.perldoc.com/perl5.8.0/pod/perlfunc.html|perlfunc] for new never used functions... like [http://www.perldoc.com/perl5.8.0/pod/func/ucfirst.html|ucfirst] is good when needed too:)
 


Enlil says autovivify... try this:use strict;use warnings;use Data::Dumper;my %hash;if($hash{this}{that}){print "nope";}print Dumper \%hash; :) i just meant be careful how you check for existence and whatnot:)




<Alexander> castaway, was "unique for each environment.." for me? (and if so, is that a "yes, each user will safely get the data unique to them and them alone"?)
<castaway> yes it was.. and yes they should
<castaway> (each login creates a new environment..)
<tye> Alexander, requests from different users will still hit web server processes at random so ENV variables will jump between users randomly.
castaway didnt know Alexander was talking about web server stuff.