in reply to Re^2: shift in list context buggy?
in thread shift in list context buggy?
So according to you, the demonstrated code using splice is a programmers error!
WTF did you dream that incomprehensible conclusion up from?
It is neither stated nor implied, nor logically derivable from anything I posted.
You just made it up in an attempt to misdirect.
Of course shift should return an empty array which is false.
Why "of course"?
splice can return multiple values, so when it has nothing to return, it makes sense to return an empty list.
Conversely, shift can only ever return a single value; so why would it ever return a list. Even an empty one.
Of course, it could return an empty list, and that would allow your construct to 'work'.
But it doesn't and never has! And -- other than to make your peculiar construct work -- there is no reason why it should.
Thus, it is your construct that is at fault.