comment on

Wow, thanks for the examples. It would seem "simple usage" is not what people would assume it is. I will go file a bug report against PathTools, but it may be instructive to see how easy it is to fall into this trap. Here is the line of code in File::Spec::Win32.pm that caused me all the grief:

  $tmpdir = $_[0]->_tmpdir( @ENV{qw(TMPDIR TEMP TMP)},
                            'SYS:/temp',
                            'C:\system\temp',
                            'C:/temp',
                            '/tmp',
                            '/'  );
[download]

Sure looks innocent, huh? Of course the 'fix' will be to change the references to 'simple' ones,

  $tmpdir = $_[0]->_tmpdir( $ENV{TMPDIR},
                            $ENV{TEMP},
                            $ENV{TMP},
[download]

And in answer to Skeeve, yes, I am a "bug-magnet"

In reply to Re^3: Autovivification sucking the life out of me by shenme
in thread Autovivification sucking the life out of me by shenme

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks