On Fri, 19 Nov 2004, Simon Flack wrote:
> Date: Fri, 19 Nov 2004 18:47:39 +0000
> From: Simon Flack <sf at flacks.net>
> To: tony at kasei.com, Maypole List <maypole at lists.netthink.co.uk>
> Subject: Re: [Maypole] (no subject)
>
> On Fri, 19 Nov 2004 18:23:33 +0000, Tony Bowden wrote
>> On Fri, Nov 19, 2004 at 04:48:42PM +0000, Simon Flack wrote:
>>> It would simplify things a lot, but would require turning the current
>>> inheritance tree on its head.
>>
>> Whilst I don't want to speak to the specifics of
>> Maypole::Application, which I haven't really investigated, I will
>> however say that one of my concerns about Maypole is the current
>> inheritance model - in particular the use of multiple inheritance,
>> often by doing deep hackery to add something into something else's parents.
>>
>> Finding ways of teasing this apart, so that there's much more use of
>> composition rather than inherance would IMO be a very positive step
>> forward. I'd suggest looking more in that direction than in just reversing
>> the direction of inheritance.
>
> That's pretty much what I had in mind. I just don't know how big an impact it
> is. How many apps inherit from Apache::MVC compared to Maypole::Application
> for example.
Um.. I have a couple, but then I am still using Maypole 1.5
is Maypole 2.x going to be backward compatible, can I still use simon's
perl.com and developerworks articles as reference or a starting point or
do they need updating or reworking?
Cheers,
A.
-- Aaron J Trevena - Perl Hacker, Kung Fu Geek, Internet Consultant AutoDia --- Automatic UML and HTML Specifications from Perl, C++ and Any Datasource with a Handler. http://droogs.org/autodia_______________________________________________ maypole mailing list maypole at lists.netthink.co.uk http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:57 GMT