"Use of initialized value in scalar assignment"

[kj]

The following innocent-looking one-liner:

% perl -we '$ENV{ FOO } = undef'

produces the warning:

Use of uninitialized value in scalar assignment at -e line 1

Is this a bug, or is there a good reason for this?

FWIW, I've seen this behavior only with %ENV. I got the above
using v5.8.8 on Linux.

TIA!

kj

 

[John W. Krahn]

The following innocent-looking one-liner:

% perl -we '$ENV{ FOO } = undef'

produces the warning:

Use of uninitialized value in scalar assignment at -e line 1

Is this a bug, or is there a good reason for this?

FWIW, I've seen this behavior only with %ENV. I got the above
using v5.8.8 on Linux.

What makes you think that you could set an environment variable to the
undef value? How does that make sense?

man 3 setenv


Perhaps you meant to use delete() instead:

delete $ENV{ FOO }



John

 

[John Bokma]

The following innocent-looking one-liner:

% perl -we '$ENV{ FOO } = undef'

produces the warning:

Use of uninitialized value in scalar assignment at -e line 1

Is this a bug, or is there a good reason for this?

FWIW, I've seen this behavior only with %ENV. I got the above
using v5.8.8 on Linux.

What do you expect from setting an environment variable to undef?