On Friday, March 15, 2013, Vlad Irnov wrote: > On 3/15/13, John Little <[email protected] <javascript:;>> wrote: > > Well, I know squat about Python but I presume it has a compilation phase > > like Perl, which compiles to "op codes" which are executed without, f. > ex., > > variable look ups. Vim uses a pure interpreter. > > > > Vim script is "fast enough", and has the virtue of running anywhere vim > does > > (well, not quite; anywhere a "normal" non-gui build does) with few > > dependencies, IIUC a C compiler and the standard library. > > > > Regards, John Little > > > > You are probably right. Python does compile the source code into > bytecode. It's interesting that such basic operation as "for" loop > gets >30-fold performance boost. > > Regards, > Vlad > > -- > -- > You received this message from the "vim_use" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_use" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:;>. > For more options, visit https://groups.google.com/groups/opt_out. > > It's entirely possible that the loop in question was simply left out as a compiler optimization. Modern compilers can detect no-op loops and unchanging assignments and take these things out of the compiled code.
Salman -- سلمان حلیم -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
