I don't necessarily think any of us were discussing optimization of the code base, but good coding practices to ensure we think about optimal performance while we do refactoring and addition of new features. I totally agree with you about premature optimization. But I also think it is important for the gurus among us (not me... :) ) to share their knowledge of optimal C/C++ coding techniques that the rest of us can keep in mind while we work.
:) -jay Andy Lester wrote: > > On Aug 4, 2008, at 9:28 AM, Jay Pipes wrote: > >> 100 * .001 = .1 >> >> Your point is good, though. :) > > > All of this is irrelevant, though. We're violating the 2nd rule of > Optimization Club: > > 1. The first rule of Optimization Club is, you do not Optimize. > 2. The second rule of Optimization Club is, you do not Optimize > without measuring. > 3. If your app is running faster than the underlying transport > protocol, the optimization is over. > 4. One factor at a time. > 5. No marketroids, no marketroid schedules. > 6. Testing will go on as long as it has to. > 7. If this is your first night at Optimization Club, you have to > write a test case. > > -- > Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance > > > > _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
