Re: execution speed (was speeding up xcode)
Re: execution speed (was speeding up xcode)
- Subject: Re: execution speed (was speeding up xcode)
- From: Ladd Van Tol <email@hidden>
- Date: Wed, 19 Oct 2005 17:10:29 -0700
I've written code for such a machine.
Needless to say, it's hard to write an interestingly complex application when you're coding to save every possible cycle. Remember: roughly 90% of a software engineer's time is spent doing maintenance on existing code. Therefore, it is usually best to write for clarity and maintainability first, and worry about low-level optimization when it is measurably important to do so. Successful software engineering is a balancing act -- focusing on performance above all else may ignore many other important engineering goals. Sure, I could write my own regular _expression_ library to gain a few cycles. Or I could take something off the shelf and ship on-time. As others have said, Shark is your friend. Write well-modularized and readable code, then measure to find out if you've got any hot spots.
- L
On Oct 19, 2005, at 4:12 PM, Robert Dell wrote: I sometimes wonder if we'd all see the need for newer and faster computers if everybody wrote their code as if it's running on a 48k, 1MHz machine.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden