At 04:23 PM 7/27/02 +0100, [EMAIL PROTECTED] wrote:
>Elizabeth Mattijsen <[EMAIL PROTECTED]> writes:
> > >I usually just call UNIVERSAL::isa($_[0], 'your::class::name') in
> these cases.
> >return unless UNIVERSAL::isa( $_[0],__PACKAGE__ );
>Don't you still have a 'subclass problem? Consider
Elizabeth Mattijsen <[EMAIL PROTECTED]> writes:
> At 04:03 AM 7/23/02 +1000, Ken Williams wrote:
> >> return unless ref($_[0]);
> >I usually just call UNIVERSAL::isa($_[0], 'your::class::name') in these cases.
>
> That's a good tip.
>
> I actually generalized this to:
>
>return unless UN
At 04:03 AM 7/23/02 +1000, Ken Williams wrote:
>> return unless ref($_[0]);
>I usually just call UNIVERSAL::isa($_[0], 'your::class::name') in these cases.
That's a good tip.
I actually generalized this to:
return unless UNIVERSAL::isa( $_[0],__PACKAGE__ );
This will be implemented in Thr
On Monday, July 22, 2002, at 04:22 AM, Elizabeth Mattijsen wrote:
> You should therefore _always_ check the validity of the first value
> passed to DESTROY and make sure it is what you expect it to be. If you
> don't, you're looking at indeterminate (strange) execution errors or
> segfaults.
Huh,
Huh
Huh
I think I will find this is not really a threads bug, will look at it.
Arthur
On söndag, juli 21, 2002, at 08:22 , Elizabeth Mattijsen wrote:
> This may be of interest to module authors who are looking at making
> their modules thread-safe. This is particularly important if yo
