"I don't think your if test will autovivify anything because of the short circuit behaviour of the && operator."
It is true there is no autovivification, but it certainly has nothing to do with short circuit. If it should cause any autovivification, the first defined() call already triggered it, certainly no need for that 'ne' after the && to carry it out.
What autovivification says is that, read/test a non-exist element of a container, creates the ancestors of that node automatically. This is obviously not what is going on here.
In reply to Re: Re: split, Use of uninitialized value
by pg
in thread split, Use of uninitialized value
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |