Re: Annouce: DBIx::Class, a.k.a "taking the easy way out"

[prev] [thread] [next] [Date index for 2005/07/26]

From: Sebastian Riedel
Subject: Re: Annouce: DBIx::Class, a.k.a "taking the easy way out"
Date: 07:53 on 26 Jul 2005
Am 26.07.2005 um 03:15 schrieb John Siracusa:

> On 7/25/05 6:12 PM, Michael G Schwern wrote:
>
>> I really don't know how real plugin architectures deal with this  
>> sort of
>> problem [...]
>>
>
> Ideally, plug-ins have a single, well-defined interface.  For example,
> imagine an image viewer that supports plug-ins for image formats.  The
> plug-in API would say something like, "We feed you a file path, you  
> return a
> buffer full of 16-bit-per-component color values in ARGB format."

So there is only one (your) way of doing things?
My point is that there are multiple levels of plug-in APIs, what you  
explain is an app level one while multiple inheritance would be  
"framework" level.
Multiple inheritance can be tricky at times (as schwern pointed out),  
but "being able" to extend everything is definately a good thing.


--
sebastian

(message missing)

Re: Annouce: DBIx::Class, a.k.a "taking the easy way out"
Sebastian Riedel 07:53 on 26 Jul 2005

Delegation vs Hooks (was: Annouce: DBIx::Class, a.k.a "taking the easy way out")
=?ISO-8859-1?Q?Ask_Bj=F8rn_Hansen?= 23:27 on 26 Jul 2005

Generated at 16:37 on 28 Jul 2005 by mariachi v0.52