[Coco] Re: optimizing

[Gene Heskett]

On Tuesday 09 December 2003 18:53, Roger Taylor wrote:
>At 05:20 PM 10/18/2003 -0400, you wrote:
>With modern, super-scalar processors, a human CAN produce better
> code than an optimizing compiler, HOWEVER, it takes a lot of extra
> work.
>
>>The general rule is: don't optimize before it works.  Once it
>> works, you profile the code, see where it spends most of its time,
>> and optimize that small part.  Because a lot of the time, the
>> optimizations you make, without knowing what gets used the most,
>> are not very useful, and make the code harder to maintain.
>>
>>I didn't get my B.Comp.Sci. for nothing. ;)
>
>Define "optimize".

:-)

>If John Doe is speed-optomizing Joe Doe's space-optimized code, what
> happens?
>
>Anyway, my own general rule (derived from a degree in hardknocks) is
> to not save all of the optimizing for last, so it won't be that
> much extra work.
>
>cheers
>
Heck, if I want it optimized, I do it in asm in the first place.  I 
have that same degree from the University of Hard Knocks, hanging on 
the wall right above me.

>
>----------
>Roger Taylor

-- 
Cheers, Gene
AMD K6-III at 500mhz 320M
Athlon1600XP at 1400mhz  512M
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.