From: Bruce W. <br...@mi...> - 2004-02-27 04:41:49
|
> Are there any differences between putting code in a noloop block > and putting it > in an if $Startup test? Other than the fact that the if $Startup > would not have > to be tested on each loop if the code is in a noloop block, of course. > > Also, some questions on what should be outside of the code loop: > I presume you would want to keep static set_states outside of the > code loop, > correct? > What about subroutine procedures? I have lots of subs that get > called in various > tests from the main code loop, as well as from web/bin routines. > Should I move > these to a noloop block? Would it be more efficient, or does it matter? Startup code and noloop code are similar. We usually use noloop code if we are creating global variables that are needed to define objects (e.g. pass a list of playlist to create voice commands). I think I've looked at defineing subs once, out of the loop -vs- leaving them in the loop and did not notice a difference. Perl must be clever on its own that way. If you want to review how code is arranged, you can look at the actual code that gets evaled: data_dir/mh_temp.user_code Bruce |