Re^4: Better Inside-Out Objects :)

What happens when someone tries to throw one of these objects at Data::Dumper et al?

That's a problem with Inside-Out Objects in general.

What happens when someone tries to create an object on the fly by loading data into a hash reference manually and then blessing it into an object?

They ought to be shot. Constructors (incl cloning and deserializing constructors) exist for a reason. You can't expect to clone an object by copying it's bytes or it's fields.

Comment on Re^4: Better Inside-Out Objects :)

Replies are listed 'Best First'.
Re^5: Better Inside-Out Objects :) by xdg (Monsignor) on Oct 07, 2006 at 03:25 UTC
That's a problem with Inside-Out Objects For Data::Dumper, yes, because its OO approach is broken. Not so for Storable. I was speaking generically. You can't expect to clone an object by copying it's bytes or it's fields. Ditto for changing its properties by directly accessing its hash, which is why this is a mess. -xdg Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.	[reply]

Replies are listed 'Best First'.

Re^5: Better Inside-Out Objects :)
by xdg (Monsignor) on Oct 07, 2006 at 03:25 UTC

That's a problem with Inside-Out Objects

For Data::Dumper, yes, because its OO approach is broken. Not so for Storable. I was speaking generically.

You can't expect to clone an object by copying it's bytes or it's fields.

Ditto for changing its properties by directly accessing its hash, which is why this is a mess.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

[reply]