Re: How could we "implement" Open Classes in Perl ?

Unless you go to extraordinary length to close them, most implementations, including the defacto blessed-reference based and inside-out implementations of classes allow you to add or replace methods at runtime.

For my interest, what is it that you find so desirable about open classes?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re: How could we "implement" Open Classes in Perl ?

Replies are listed 'Best First'.
Re^2: How could we "implement" Open Classes in Perl ? by Alien (Monk) on Jun 27, 2008 at 07:54 UTC
I think I like them because you don't have to spend all that time on design patterns.	[reply]
Re^3: How could we "implement" Open Classes in Perl ? by BrowserUk (Patriarch) on Jun 27, 2008 at 07:59 UTC
Sorry, but you'd have to expand that a little before I'll understand your reasonimg? Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^4: How could we "implement" Open Classes in Perl ? by Alien (Monk) on Jun 27, 2008 at 08:02 UTC
I like to design as I code. I'm not really the adept of "thinking first,and coding second" :)	[reply]
Re^5: How could we "implement" Open Classes in Perl ? by BrowserUk (Patriarch) on Jun 27, 2008 at 08:43 UTC
Re^6: How could we "implement" Open Classes in Perl ? by dragonchild (Archbishop) on Jun 27, 2008 at 14:39 UTC
Some notes below your chosen depth have not been shown here