Sam Holden wrote:
Scott R. Godin writes:
I guess I'm curious whether it even makes any sense to continue in an OO
vein for this .. I had visions of being able to just
package Subscriber::Database;
our ($db, $user, $pass) = (dbi:Path:here, username, password);
package main;
my $db =
On Sun, 16 Jan 2005, A. Pagaltzis wrote:
* Sam Holden [EMAIL PROTECTED] [2005-01-15 17:09]:
Only inherit when you have an ISA relationship.
I just want to chime in to agree.
Inheritance is greatly overrated and widely abused. It is almost
always the very last option you should consider.
Scott R. Godin writes:
I guess I'm curious whether it even makes any sense to continue in an OO
vein for this .. I had visions of being able to just
package Subscriber::Database;
our ($db, $user, $pass) = (dbi:Path:here, username, password);
package main;
my $db =
Title: RE: Subclassing a mailer
Well here I have this Subscriber object, let's call it. They
signed up
on a web form, and I've poulated the object with the validated data.
what would I like to do with the Subscriber?
o send them a welcome mailing
o snailmail - add them
Scott R. Godin writes:
[snip disucssion of iheriting from a mailing class]
what would I like to do with the Subscriber?
o send them a welcome mailing
o snailmail - add them to tommorow's list of mailing labels along
with a marker to the correct template
o e-mail - send them a
* Sam Holden [EMAIL PROTECTED] [2005-01-15 17:09]:
Only inherit when you have an ISA relationship.
I just want to chime in to agree.
Inheritance is greatly overrated and widely abused. It is almost
always the very last option you should consider. Aggregation is
way underrated and should be used
Scott R. Godin wrote:
For a project I'm on, I'm pondering whether or not to subclass one of
the various Mail::* implementations out there, with an eye for
Mail::Mailer.
Does anyone have any recommendations in this regard? gotchas things I
should watch out for ? pointers? examples? :)
I don't
On Thu, Jan 13, 2005 at 10:02:32AM -0500, Scott R. Godin wrote:
For a project I'm on, I'm pondering whether or not to subclass one of
the various Mail::* implementations out there, with an eye for
Mail::Mailer.
Does anyone have any recommendations in this regard? gotchas things I
Randy W. Sims wrote:
Scott R. Godin wrote:
For a project I'm on, I'm pondering whether or not to subclass one of
the various Mail::* implementations out there, with an eye for
Mail::Mailer.
Does anyone have any recommendations in this regard? gotchas things
I should watch out for ? pointers?
Title: RE: Subclassing a mailer
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
Yves Orton wrote:
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
For a project I'm on, I'm pondering whether or not to subclass one of
the various Mail::* implementations out there, with an eye for
Mail::Mailer.
Does anyone have any recommendations in this regard? gotchas things I
should watch out for ? pointers? examples? :)
--
Scott R. Godin
Laughing
12 matches
Mail list logo
