Tom Christiansen <[EMAIL PROTECTED]> writes:
> >What I think might be more interesting or useful would be to have
> >another undef type. Call it uninit. THis would be only used for data
> >that hasn't been initialized. Then there would be two warnings one
> >for unitialized and one for using undef.
>
> Argh, no!
So you wouldn't be in favour of:
my Dog $spot;
print defined($spot) ? 'defined' : 'undefined'; # undefined
print $spot->isa('Dog') ? 'Dog' : 'not dog'; # Dog;
then?
Bang goes that RFC...
--
Piers
- Re: Pre-RFC - "use warnings" by default for al... Chaim Frenkel
- Re: Pre-RFC - "use warnings" by default for al... Michael G Schwern
- Re: Pre-RFC - "use warnings" by default for al... Tom Christiansen
- Re: Pre-RFC - "use warnings" by default for al... Michael G Schwern
- Re: Pre-RFC - "use warnings" by default for al... Chaim Frenkel
- Re: Pre-RFC - "use warnings" by default for al... Chaim Frenkel
- Re: Pre-RFC - "use warnings" by default for al... Tom Christiansen
- Re: Pre-RFC - "use warnings" by default for al... Michael G Schwern
- Re: Pre-RFC - "use warnings" by default for al... Tom Christiansen
- Re: Pre-RFC - "use warnings" by default for al... Michael G Schwern
- Re: Pre-RFC - "use warnings" by default for al... Piers Cawley
- Re: Pre-RFC - "use warnings" by default for al... Michael G Schwern
- Re: Pre-RFC - "use warnings" by default for al... Bart Lateur
- Re: Pre-RFC - "use warnings" by default for al... Piers Cawley
- Re: Pre-RFC - "use warnings" by default for al... Piers Cawley
