[Chicago-talk] 2 subclasses or Multiple inheritance

me at heyjay.com me at heyjay.com
Sat Mar 20 10:40:43 CST 2004


And I understand what you say, but at present it seems like my base class
would be:

package My::Broker;


----- Original Message ----- 
From: "Young, Aaron" <Aaron.Young at citadelgroup.com>
To: "Chicago.pm chatter" <chicago-talk at mail.pm.org>
Sent: Saturday, March 20, 2004 10:27 AM
Subject: RE: [Chicago-talk] 2 subclasses or Multiple inheritance

i would recommend the subclass approach, where i work, we have something
that sounds exactly like what you are doing, and the subclass approach
has worked well for us.

if you add many more brokers, it's likely that some code will eventually
be shared, and you'll be able to move those methods into your
superclass, this technique will give you plenty of room to grow in the

Aaron F Young
Broker Reconciliation
Operations & Portfolio Finance
Citadel Investment Group LLC

> -----Original Message-----
> From: Jay Strauss [mailto:me at heyjay.com]
> Sent: Friday, March 19, 2004 11:03 PM
> To: chicago-pm
> Subject: [Chicago-talk] 2 subclasses or Multiple inheritance
> I have a class which connects to Ameritrade (broker), and I
> have another
> class which connects to InteractiveBrokers.  Both of these
> classes have
> methods quote, connect, disconnect.  The class for
> InteractiveBrokers has a
> bunch of others too.  While the method names are the same their
> implementation is totally different, as are their required
> input parms.
> The classes don't share any of the same code, and I don't see
> them sharing
> any/much in the future.
> I'd like to be able to plug in other brokers as necessary.
> So my question is, do I make a base class like "broker" and make a
> Ameritrade and InteractiveBrokers that inherit from broker,
> or do a make a
> broker that inherits from Ameritrade and InteractiveBrokers?
> Thanks
> Jay
> _______________________________________________
> Chicago-talk mailing list
> Chicago-talk at mail.pm.org
> http://mail.pm.org/mailman/listinfo/chicago-talk


This e-mail contains information that may be confidential and
proprietary. It is to be read and used solely by the intended recipient(s).
Citadel and its affiliates retain all proprietary rights they may have in
information. If you are not an intended recipient, please notify us
immediately either by reply e-mail or by telephone at 312-395-2100
and delete this e-mail (including any attachments hereto) immediately
without reading, disseminating, distributing or copying. We cannot give
any assurances that this e-mail and any attachments are free of viruses
and other harmful code. Citadel reserves the right to monitor, intercept
and block all communications involving its computer systems.

Chicago-talk mailing list
Chicago-talk at mail.pm.org

More information about the Chicago-talk mailing list