Re: Re: Re: Re: Re: Re: Re: Re: Why breaking can() is acceptable

[tilly]

On traits, I have seen that lots of people have lots of verbiage about it, but I've skipped that because my provisional opinion at Re: Re: very simple per-object mixins about mixins is also my provisional opinion on traits. They are a bad idea unless they are done a lot, with a relatively few examples being done. Then they become good.

On the version of can that you provided, I assume that you had a typo, you wanted the return to be return sub { $self->$method(@_) }; In which case your solution becomes the same as the one that simonm came up with at Re: Re: Re: Re: Re: Re: Re: Why breaking can() is acceptable, and my reply at Re: Re: Re: Re: Re: Re: Re: Re: Why breaking can() is acceptable. My point that I'd expect people to come up with this answer and not noticed its issues has been strengthened by the fact that that has now happened twice in a row.

If you want to take Class::FlyweightWrapper to the next level, be my guest. I'm not particularly interested in it because I'm not using it. It wasn't hard to implement the first time, and the fact that I'm not using it means that I don't have any intuition on where people will have issues with it.

On the other 2 implementations. While neither is aimed for widespread use, both are functional enough to be used in a local project. I wouldn't be surprised if a lot of real production code that uses AUTOLOAD is at a similar level, excepting the fact that real code has become longer because people have kept on adding stuff to it.

About diversity, that is a good thing about Perlmonks. You're right about the likely outcome, but hopefully this thread gives you some perspective about why at least some people won't pay as much attention as you would like to your insisting.

[stvn]

Okay, we agreed to let this one drop, but i just have say one thing about this...

... but hopefully this thread gives you some perspective about why at least some people won't pay as much attention as you would like to your insisting.

The only people I expect to pay attention to my insisting, is those who work for me, and whose code I am (ultimately) responsible for. I know full well I cannot control the whole of CPAN, and the perl community at large. But IMO we should all strive to write software that is robust and solid and behaves in a predicatable way. Just saying "it's broke, so what" to me is not acceptable. Now i know you were alot times just playing devil's advocate to make me think, and believe me, you suceeded in that, but in the end I have to say I still think it should work, and I don't think that too unreasonable a goal to strive for.
-stvn