From: Joel VanderWerf <vjoel@...>
Date: 2006-06-10T04:59:24+09:00
Subject: Re: Why the lack of mixing-in support for Class methods?

Alder Green wrote:
> On 6/9/06, Joel VanderWerf <vjoel@path.berkeley.edu> wrote:
>> Here's another shortcut, dunno how original it is. I don't like the
>> #import (or #include!) suggestions because they take control away from
>> the module. In most cases, the module will know best which (if any)
>> class methods to contribute.
> 
> Assuming #import would have a callback-hook like #included
> (#imported?), how would the locus of control shift from where it is
> right now?

The #imported callback might help (and it would inevitably be requested
if it were not provided), but then the module author has to decide how
to handle each of #included, #imported, and #extended.

I'm still leaning towards having just one method, include, that is
available to client classes to "use" the module in typical cases. The
module decides what gets included at the instance and class levels.

-- 
      vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407