Top-level command invokations not compiled

#1 08-27-2008, 08:08 AM

Hi,

There are many places where the following note is mentioned:

"Top-level invokations of commands are not byte-compiled, so be aware to put
most of them into procedure(s), so they run faster." -...or something like
that.

Well, why aren't they compiled? What is the reason to aviod compiling them?

--
Pozdrawiam! (Regards!)
Googie

#2 08-27-2008, 08:36 AM

On Aug 27, 2:08 pm, Googie <n...@spam.0rg> wrote:
> Hi,
>
> There are many places where the following note is mentioned:
>
> "Top-level invokations of commands are not byte-compiled, so be aware to put
> most of them into procedure(s), so they run faster." -...or something like
> that.
>
> Well, why aren't they compiled? What is the reason to aviod compiling them?

Because since they are toplevel they will run just once, hence the
cost of compiling them will not be diluted over several runs of the
bytecode. See Miguel's recent summary on this:

http://groups.google.com/group/comp....1bafa752a80104

-Alex

#3 08-27-2008, 08:39 AM

On 27 Aug., 14:36, Alexandre Ferrieux <alexandre.ferri...@gmail.com>
wrote:

> Because since they are toplevel they will run just once, hence the
> cost of compiling them will not be diluted over several runs of the
> bytecode. See Miguel's recent summary on this:
>
> http://groups.google.com/group/comp....e_frm/thread/d...

If you want to force compilation, put the code in question into an "if
1 { ... }" block.
Code in procedures still has the advantage that local variables can be
dealt with more efficiently.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode