Erik Hofman wrote:
Sounds good, implement first, optimize later.
The standard Unix developer's rules (from memory):
1. Make it work. 2. Make it right. 3. Make it efficient.
I've worked as a consultant on too many projects where people have done these steps in reverse, never with a happy outcome. #3 usually produces code so obfuscated that #2 and #1 become difficult or impossible.
Yes, I can imagine making it efficient often produces hard to read code..
Erik
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
