Re: Class::Data::Inheritable and persistence.

[prev] [thread] [next] [Date index for 2004/07/08]

From: Michael G Schwern
Subject: Re: Class::Data::Inheritable and persistence.
Date: 20:13 on 08 Jul 2004
On Thu, Jul 08, 2004 at 09:44:29AM +0100, Tony Bowden wrote:
> On Wed, Jul 07, 2004 at 06:59:15PM -0400, Vince Veselosky wrote:
> > I suppose it is fine, as long as none of the data is meant to be changed 
> > at run time. 
> 
> Changing class data at runtime will have lots of strange effects
> regardless of your environment. That's why its class data and not
> instance data.

Class data just means its common to all objects of the class.  There's
nothing inherent to class data that it can't change at run time. [1]
Unless you do something silly like copy class data into each object, it
should be perfectly safe to change class data.


[1] I'm speaking in the general sense here.  There's lots of application
specific reasons why you shouldn't change class data, but there's also
why you wouldn't change object data.

        -- 
        Michael G Schwern        schwern@xxxxx.xxx  http://www.pobox.com/~schwern/
WOOHOO!  I'm going to Disneyland!
	http://www.goats.com/archive/980805.html

(message missing)

Class::Data::Inheritable and persistence.
Vince Veselosky 21:56 on 07 Jul 2004

Re: Class::Data::Inheritable and persistence.
Tony Bowden 22:03 on 07 Jul 2004

Re: Class::Data::Inheritable and persistence.
Vince Veselosky 22:59 on 07 Jul 2004

Re: Class::Data::Inheritable and persistence.
Tony Bowden 08:44 on 08 Jul 2004

Re: Class::Data::Inheritable and persistence.
Vince Veselosky 10:51 on 08 Jul 2004

Re: Class::Data::Inheritable and persistence.
Michael G Schwern 20:13 on 08 Jul 2004

Re: Class::Data::Inheritable and persistence.
Tony Bowden 23:13 on 08 Jul 2004

Re: Class::Data::Inheritable and persistence.
Michael G Schwern 00:45 on 09 Jul 2004

Re: Class::Data::Inheritable and persistence.
Perrin Harkins 03:51 on 09 Jul 2004

Generated at 11:34 on 01 Dec 2004 by mariachi v0.52