> From: Cees Hek > > Since the list has been quiet for the last little while, I thought I > would stir things up a bit. There was a thread about Class::Trait > recently on perlmonks that caught my attention: > > http://perlmonks.org/?node_id=509958 > > I had looked at Traits before, but never found the time to look into > them carefully.
Hi Cees, I just came across your post on perlmonks http://www.perlmonks.org/?node_id=510005 The reply pointing to Class::C3 looks interesting - I'd never heard of that module before. However, it seems that there is still a problem coming up with a satisfactory solution - if a developer is using a number of plugins, and there are one or more method collisions, it's going to be hard for said developer to resolve which one should take precedence. IMO - none should - it should just error - or at least raise a warning. If there is a warning, then maybe there could be a mechanism for the developer to programmatically specify a preference. If there is a collision from multiple inheritance rather than mixins, then maybe the Class::C3 approach might be worth investigating... Dan --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
