At 11:51 AM + 12/23/01, Jean-Michel Hiver wrote:
Maybe the way to do it would be to have a Serializable class that could have
the following methods:
freeze($self) : SCALAR
thaw ($class) : OBJECT
clone($self) : OBJECT;
_freeze($self): SCALAR
_remove_transient_attributes($self);
Hmmm... Maybe
By attribute do you mean an element of the data structure that is blessed
in the object? Or do you mean some sort of new attribute you would assign
a
new Serializable data type (ala something to suggest for Perl 6).
I think that what Brian was trying to say is that you could mark an object
doesn't it seem like there should be a way to denote object
data as transient so that it doesn't get serialized by
Storable, etc?
i've solved this problem in the past by writing a
class-specific serialization method that undefs things i
don't want serialized. but it seems like something that
On Sat, Dec 22, 2001 at 06:11:33AM -0800, brian moseley wrote:
doesn't it seem like there should be a way to denote object
data as transient so that it doesn't get serialized by
Storable, etc?
I'd love that as well. For example, when persisting Cache::Object
instances I manually strip out
At 10:19 PM 12/22/2001, DeWitt Clinton wrote:
On Sat, Dec 22, 2001 at 06:11:33AM -0800, brian moseley wrote:
doesn't it seem like there should be a way to denote object
data as transient so that it doesn't get serialized by
Storable, etc?
I'd love that as well. For example, when
On Sat, 22 Dec 2001, brian moseley wrote:
doesn't it seem like there should be a way to denote
object data as transient so that it doesn't get
serialized by Storable, etc?
dammit, i keep deleting peoples' replies before i am able to
reply to them myself.
gunther's suggestion was to use
At 03:33 PM 12/23/2001, brian moseley wrote:
On Sat, 22 Dec 2001, brian moseley wrote:
doesn't it seem like there should be a way to denote
object data as transient so that it doesn't get
serialized by Storable, etc?
dammit, i keep deleting peoples' replies before i am able to
reply to
