> At 04:15 PM 4/3/2003 -0500, Thomas, Mark - BLS CTR wrote: > >So my question boils down to this: Can I override methods > that act on > >the superclass' object, without having to instantiate a new object? > > And my question in response: Didn't my attached code accomplish that?
Your code instantiated a My::Table::HTML object. This is normal OO, and in fact I do something similar with My::Table::Header and My::Table::Row subclasses (that is, I instantiate their objects and add them to the table). I omitted them from my original description for simplicity. But I'm treating these "output classes" differently. A My::Table object will already be built. I don't want My::Table to know about My::Table::HTML or any other output method until the method is called on a My::Table object. In other words, I want them to act like My::Table object methods, but I want to separate them into (optional) modules. Perhaps I shouldn't have called them "subclasses" as they do not represent a different object. Is this making sense? Perhaps there's a better way to do it. -- Mark Thomas [EMAIL PROTECTED] Internet Systems Architect User Technology Associates, Inc. $_=q;KvtuyboopuifeyQQfeemyibdlfee;; y.e.s. ;y+B-x+A-w+s; ;y;y; ;;print;; _______________________________________________ Perl-Win32-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
