> Well said, Ted. Computers can crunch a ton of stuff, and especially > with today's remarkable processing power, the guy is perhaps focused on > the wrong aspect. My POV: Always write code that others can maintain, > because even if that's you, you don't want to be cursing it (or > yourself) years down the line when things need to change.
Agreed. Brevity isn't always maintainability, and as Ted points out, his example isn't even as correct as the IsNullOrEmpty comparison others suggested . A function of half a dozen lines is sometimes far easier to read than one of 5 lines. I try to code to make things clearly readable and explicit and only shorten/compress the code if needed for optimization. If I feel the optimized code is too hard to read, I leave the non-optimized code in comments as well. -- Derek _______________________________________________ Post Messages to: ProFox@leafe.com 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.
