> ahh no, nothing in that regard.. What I want is to add some of said
> capabilities to another module that I'm creating that's unrelated to any
> thing to do with mailing. The object merely tracks some client data. In
> some instances I'll want to send an e-mail to the address in the client
> data, if they have supplied one. The body of the mail may be created
> from a Text::Template or some other source, possibly, but essentially I
> would like to, at some branch in the end-user code, hand it off to be
> mailed out, but with certain prerequisites determined by my
> own object.
IMO this is probably a bad reason to subclass. It sounds much more appropriate to do a HAS-A relationship instead of a IS-A relationship.
For instance your code at some point is going to call a method that causes an email to be sent. At that point you would create a MIME::Lite object and use it to create and send the mail as needed. Doing this via ISA semantics doesnt make a lot of sense to me.
If you were overriding some behaviour in the mail module it would be a different story.
Regards,
Yves
