From: matz@... (Yukihiro Matsumoto)
Date: 2001-06-07T01:30:22+09:00
Subject: [ruby-talk:16269] Re: Strange idea... exporting from a scope

Hi,

In message "[ruby-talk:16264] Re: Strange idea... exporting from a scope"
    on 01/06/06, Guillaume Cottenceau <gc@mandrakesoft.com> writes:

|> Could you tell me how dirty it is?  Although I know it's kinda dirty.
|
|It's a bit hard to explain, that's why I said "in my opinion". I think it
|has to cope with the fact that the programmer will use explicit sub block
|(either by {} or by begin/end) while explicitly local variables will be
|'declared' (that is, first used, with the assignment operator) inside the
|block and still be valid when the block exits.

hmm, Ruby's {} and begin/end are not really a scoping construct.

|That's why I asked you if you think of this new behaviour as: we'll use <>
|99% of the time, and || when we know we want to export the variables
|outside the block.

If I introduce <>, I think you will use <> 99% of the time.

							matz.