>> Put the weapons away. Discuss.<< Geez, such rules. Hold on... List of weapons removed from the email in case it is sniffed by the gov't department of snoopers. <g>
I also agree with your associate, especially if there is a possibility for subclassing and overriding one of the smaller methods. I recently have been working on a conversion where the code for a table is bottled in one method. Not a lot of code per-se, but I need to override a small part of it. If the original developer put in some hook methods, or broke up methods into smaller chunks I would not have needed to override the entire method to tweak one line of code. I don't see the determining factor as the number of lines of code (although there are some reasonable counts we can consider as smellin' bad), rather designing the appropriate amount of flexibility into the class. This is a general rule, and one that is decided on for a specific case. Rick White Light Computing, Inc. www.whitelightcomputing.com www.swfox.net www.rickschummer.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
