On Mar 12, 2005, at 5:48 PM, chromatic wrote:
To make this work, the easiest approach seemed to be overriding parts
of
Module::Build that aren't entirely public.
Typically this means we need to solidify and make public those areas of
the API. That's sort of the development model I tend to use (for
better or worse) - create private-ish methods and make them public when
someone asks for them to be public.
I'm looking for feedback in
three areas:
- is there a cleaner way to do this?
- is the idea something that Module::Build might support?
- if yes to the previous question, what changes should I make to fit
with your ideas of how Module::Build ought to work?
I've downloaded it and taken a very quick look, but haven't had time to
really examine it. It looks good, but the main problem is something
that's not very easy to solve: since you're subclassing M::B, it means
someone can't use both your value-added subclass and someone else's
value-added subclass. In other words, it would be nice to make this
some kind of Mix-In or Decorator or Plugin thingy.
-Ken
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
|
