On dimanche 18 janvier 2009, nando wrote: > After reading all the comments about speed, optimization, etc, > do not forget that an optimizing compiler will absolutely > poduce faster execution time: > Since this code reads no data, saves no data and doesn't print any > calculated data, then why even perform GetSubstring when nobody > cares about what the result is. An optimizing C compiler most likely > would compile to only execute the > t= Timer and > Print Timer - t > shich produces lightning fast times. > Why? Nobody will ever see the data computations performed inside the loop. > I recently did see optimized code disassembled for a small C program and > since nothing was printed nor saved, there was no code to run and the only > execution was RETURN. > Be careful testing code and making comparisons amongst languages because > the tests do not perform and prove unless the test is relatively meaningful > and results summed over a period of time testing. > Don't forget there are many ways to program solving a problem and > there are good and bad ways, easy and hard, fast and slow, efficient and > not. Spending a whole wack of time to prove saving 2 seconds may or may not > be futile and can or can not prove anything or nothing. > I use Gambas 1.17 for a large real-time 200 user mulit-connected program. > It performs well. > My appreciation to Benoit. > -Fernando >
Don't worry, the Gambas compiler optimizes almost nothing (this is done by the interpreter), and so never removes code. :-) -- Benoit Minisini ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user