in reply to Re: Re: Re: Feedback on Class::Container
in thread Feedback on Class::Container

samtregar wrote:
Class::MethodMaker has a method maker called "object" that declares a slot to be of a particular object type.

Oh, I see. Thanks for the clarification. However, this seems quite orthogonal to Class::Container. One might want to use Class::Container to create the objects with the proper parameters, then use Class::MethodMaker to create interfaces to the objects, possibly using the proxies Class::MethodMaker provides.

It's quite possible that someone would want to use both in the same project, but that doesn't suggest to me that they should be in the same module.

-Ken
  • Comment on Re: Re: Re: Re: Feedback on Class::Container

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Feedback on Class::Container
by samtregar (Abbot) on Jul 01, 2002 at 05:30 UTC
    Given the width of the Class::MethodMaker API I'd be surprised if any OO method generation was truly orthoganal to it! After all, the main purpose of your module is to provide a new() for sub-classes that performs certain convenient functions with respect to composition. That sounds a lot like the what many of the method makers in Class::MethodMaker do already.

    However, I'm not meaning to suggest that having Class::Container as a separate module is bad. People may want to use it who have no need for the larger functionality of Class::MethodMaker.

    As I understood your question, you asked if your new module fit anywhere in the existing OO landscape. I happen to think it does. Whether you choose to put it where I think it might fit is another question entirely.

    -sam