Re: Inconsistency in scoping during module_eval?

On Mon, 31 Jul 2006, Charles O Nutter wrote:

> in 1.8, constant scoping within a block is decided at compile time, and 
> so is scoped in the scope where the block is created. In this case, that 
> means all constants within a block, even a module_eval block will be 
> defined at the level at which module_eval was called.

> in 1.9, constant scoping is determined at runtime, so this example would 
> scope the constant within the Foo module, and defined? BAZ at the top 
> level will return nil.
>
> Is that about right?

Yes, except that for a long time, 1.9 did just like 1.8, so it's only with 
fairly recent 1.9 snapshots that you get the "new" behaviour. I put "new" 
in quotes because the "new" behaviour can also be found in Ruby 1.6, 1.4, 
etc. until a rather late version of 1.7.

I welcome the "new" behaviour. Static scoping of constants really made 
some things difficult or impossible, because then you can't have 
user-defined things that work like class..end blocks.

  _ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - t駘:+1.514.383.3801 - http://artengine.ca/matju
| Freelance Digital Arts Engineer, Montr饌l QC Canada