Re: [Module::Build] [RFC] [PATCH] Action plugins

[Randy W. S. <Ra...@Th...>]

On 12/3/2003 11:01 PM, Ken Williams wrote:

  > Hi Randy,
> 
> I'm not trying to ignore you, I swear - I just keep wanting to make a 
> little prototype of what I had in mind for a plugin architecture too, 
> and I thought it might be better to do it independently first and then 
> we can compare advantages & disadvantages of each.

No problem. I guess some people do have a life outside of writing code ;).

> Several of the points below are advantages of any plugin scheme we 
> settle on, and I'm still quite keen on getting *something* done.  If I 
> can't get off (or on, I guess) my butt and write some code of my own, my 

Yeah, I don't claim my solution is the best. In fact, it's really not 
much like what I originally planned; it evolved quite a bit into what it 
is now. Like I said before, I'm mainly thinking about the 
compiling/linking code, and I see plugins as an elegant solution to the 
current problems...

> default action will be to just apply your patches.

Please don't apply my patch; it's still a prototype, and I need to clean 
it up a bit. I need to reorganize it by splitting M::B::Action, so that 
M::B::Action remains a base class, and the other /stuff/ gets put into 
something like M::B::ActionManager which will be responsible for 
scanning plugins and dispatching actions.

 >  I do very much appreciate the time you've spent.
 >
> Also, have you had a chance to take a look at ExtUtils::CBuilder?  How 
> do you see it fitting in with a plugin scheme?  My goal with it was to 
> make something that would be generically useful, not just as a plugin 
> for Module::Build.

I will try to post something this evening when I have more time to put 
my thoughts together into something coherent. =)

Regards,
Randy.