Re: [MacPerl] defining variables if not already defined

[Ken Williams <ken@forum.swarthmore.edu>]

rees_joel@fujicomp.co.jp (Joel Rees) wrote:
>Does my() always operate at compile time? Does that mean that my hopes 
>for easy run-time allocation must be dashed?

I don't understand, why would you want to?  It sounds like an XY problem.

># The following definition might be in external source.
>my $pig = atan2( 1, 1 ) * 4;

If it's in an external file, then its scope won't extend to this file. 
That's the main point of having lexical scope.

># . . .
># Then we might use the full pig somewhere:
>print "full pig is $pig\n";

[...]

>Or do I over-interpret the assertion that my() does its stuff at compile 
>time? This is an important issue for me, because, when I start coding 
>full apps, I want to be able to depend (for natural version control and 
>similar things) heavily on distinguishing compile-time from run-time, and 
>on sometimes postponing compile-time events.

Why?  What's the goal?  What does compiletime/runtime have to do with
version control?

In general, Perl does not necessarily specify which things are done at
runtime and which things are done at compile time, though there are a
few obvious exceptions like eval, use, require, do, local, BEGIN, etc.  




# ===== Want to unsubscribe from this list?
# ===== Send mail with body "unsubscribe" to macperl-request@macperl.org