I forgot to cite the link about where I got these 2
rules of my previous msg, it is at :
[[
http://www.csl.cornell.edu/courses/ece314/tutorials/pike_C.html
]]
>>But as Mr Pike states it (those are even his first 2 rules) :
>><<
>> Rule 1. You can't tell where a program is going to spend its time.
>>Bottlenecks occur in surprising places, so don't try to second guess
>>and put
>>in a speed hack until you've proven that's where the bottleneck is.
>>
>>Rule 2. Measure. Don't tune for speed until you've measured, and even
>>then
>don't unless one part of the code overwhelms the rest.
>> >>
>>
>>Thus to prove where the bottlenecks are, and also to do measurements,
>>we definitely need more experience in using the software. Now you
>>know where your duty is ;-) !
>>
>>
>>Best, Henri
>>
>>
>>
>>_______________________________________________
>>Texmacs-dev mailing list
>>[email protected]
>>http://lists.gnu.org/mailman/listinfo/texmacs-dev
_______________________________________________
Texmacs-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/texmacs-dev
