Re: defined: Short-cutting on || with undef only.

2001-02-19 Thread David L. Nicol
I think "defined" should be altered so that it only looks like a function, but in effect alters the tests being made by the thing that is looking at it. if (defined $x){ # slower than if ($x){ # or if($x or defined($x)) could be made faster by propagating the "defined" question up the

Re: defined: Short-cutting on || with undef only.

2001-02-16 Thread Philip Newton
On 15 Feb 2001, at 20:52, [EMAIL PROTECTED] wrote: > On Thu, Feb 15, 2001 at 10:31:34AM -0300, Branden wrote: > > With Perl 6, it will (probably) be possible to have values with boolean > > value independent of integer or string values, so that it will be possible > > to have a value that when vi

Re: defined: Short-cutting on || with undef only.

2001-02-15 Thread schwern
On Thu, Feb 15, 2001 at 08:52:01PM +0100, [EMAIL PROTECTED] wrote: > You mean the beaten-to-death ??, formely known as |||, operator? > > It has torn p5p to shreds repeatedly. Could be worse, could be url open(). duck && cover;

Re: defined: Short-cutting on || with undef only.

2001-02-15 Thread abigail
On Thu, Feb 15, 2001 at 10:31:34AM -0300, Branden wrote: > With Perl 6, it will (probably) be possible to have values with boolean > value independent of integer or string values, so that it will be possible > to have a value that when viewed as string or number will be "" or 0, but > will evaluat

Re: defined: Short-cutting on || with undef only.

2001-02-15 Thread John Porter
Branden wrote: > > I think this should be applied to the `defined' function, Oh, no, here we go again. Branden, why do you insist on dredging up every contentious issue which has already been beaten to death? Maybe you need to read the archives first. -- John Porter You can't keep Perl6 Pe

defined: Short-cutting on || with undef only.

2001-02-15 Thread Branden
With Perl 6, it will (probably) be possible to have values with boolean value independent of integer or string values, so that it will be possible to have a value that when viewed as string or number will be "" or 0, but will evaluate as true in a condition. I think this should be applied to the