Re^4: New Module Announcement: Object::InsideOut

in reply to Re^3: New Module Announcement: Object::InsideOut
in thread New Module Announcement: Object::InsideOut

Then you are back to the same performance problems encountered with Class::Std, namely you have to calculate the object ID on every access.

It is an engineering trade-off that I feel is more than justified. By storing the object ID in the object's scalar, the only thing you give up is the capability to overload the ${} operator.

Remember: There's always one more bug.

Comment on Re^4: New Module Announcement: Object::InsideOut

Replies are listed 'Best First'.
Re^5: New Module Announcement: Object::InsideOut by Aristotle (Chancellor) on Nov 04, 2005 at 14:17 UTC
And the ability to subclass foreign code without knowing about its implementation. Makeshifts last the longest.	[reply]
Re^6: New Module Announcement: Object::InsideOut by jdhedden (Deacon) on Jan 10, 2006 at 15:40 UTC
[You also give up] the ability to subclass foreign code without knowing about its implementation. As of v1.18, Object::InsideOut supports inheritance (i.e., sub-classing) of non-inside-out object classes. Remember: There's always one more bug.	[reply]

In Section Perl News