Re^2: OO in Perl 5: still inadequate

Uhm.

Wow.

All I can say is, d’oh. I don’t know why something so obvious never occured to me; sometimes I can’t see the forest for the trees.

Cool! Thanks for pointing this out.

Makeshifts last the longest.

Comment on Re^2: OO in Perl 5: still inadequate

Replies are listed 'Best First'.
Re^3: OO in Perl 5: still inadequate by xdg (Monsignor) on Jan 21, 2006 at 16:08 UTC
I don’t know why something so obvious never occured to me Don't worry about it. <grin> It happens to all of us at some time or another. Inside-out objects are unusual enough still that it takes a little more effort to pick apart the different angles on it. In my presentation, I open by stating there are three fundamental concepts for people to take away: Objects as containers versus objects as indices Encapsulation via lexical closure Memory addresses as unique identifiers Everything else is just combinations and variations of these three ideas. -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^3: OO in Perl 5: still inadequate
by xdg (Monsignor) on Jan 21, 2006 at 16:08 UTC

I don’t know why something so obvious never occured to me

Don't worry about it. <grin> It happens to all of us at some time or another. Inside-out objects are unusual enough still that it takes a little more effort to pick apart the different angles on it.

In my presentation, I open by stating there are three fundamental concepts for people to take away:

Objects as containers versus objects as indices
Encapsulation via lexical closure
Memory addresses as unique identifiers

Everything else is just combinations and variations of these three ideas.

-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]