On Sun, Apr 10, 2005 at 03:44:34PM -0700, gossamer axe wrote: > > I presume you mean "faster than C code". Of course, there was a time > > where the statement was "there isn't one thing a C project can do faster > > than an assembly project". Both statements are incorrect for some pretty > > important things like "get done" or "fix bugs". Even outside of the > > human factors side of things, there are other issues to consider. A nice > > A few newbie questions here. I thought that the lower level the code, > the faster it runs. So C runs faster than VB but Assembly runs faster > than C. I do realize it's also the talent of the programmer. >
Yes and no. A good scripting language on a good OS can outperform bad C on a pokey OS. Perl, for example, flies. Much of performance depends on what the program is doing and how. Screen input waits for the human no matter what. Routines that pass over, for example, records or lines and does the same thing to each can fly or drag, depending on the implementation. Whenever you find yourself typing foreach or while, stop and think, what will this be doing each time? -- Lan Barnes [EMAIL PROTECTED] Linux Guy, SCM Specialist 858-354-0616 -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
