[#5218] Ruby Book Eng tl, ch1 question — Jon Babcock <jon@...>

13 messages 2000/10/02

[#5404] Object.foo, setters and so on — "Hal E. Fulton" <hal9000@...>

OK, here is what I think I know.

14 messages 2000/10/11

[#5425] Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...>

18 messages 2000/10/11
[#5427] RE: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — OZAWA -Crouton- Sakuro <crouton@...> 2000/10/11

At Thu, 12 Oct 2000 03:49:46 +0900,

[#5429] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...> 2000/10/11

Thanks for the input.

[#5432] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Yasushi Shoji <yashi@...> 2000/10/11

At Thu, 12 Oct 2000 04:53:41 +0900,

[#5516] Re: Some newbye question — ts <decoux@...>

>>>>> "D" == Davide Marchignoli <marchign@di.unipi.it> writes:

80 messages 2000/10/13
[#5531] Re: Some newbye question — matz@... (Yukihiro Matsumoto) 2000/10/14

Hi,

[#5544] Re: Some newbye question — Davide Marchignoli <marchign@...> 2000/10/15

On Sat, 14 Oct 2000, Yukihiro Matsumoto wrote:

[#5576] Re: local variables (nested, in-block, parameters, etc.) — Dave Thomas <Dave@...> 2000/10/16

matz@zetabits.com (Yukihiro Matsumoto) writes:

[#5617] Re: local variables (nested, in-block, parameters, etc.) — "Brian F. Feldman" <green@...> 2000/10/16

Dave Thomas <Dave@thomases.com> wrote:

[#5705] Dynamic languages, SWOT ? — Hugh Sasse Staff Elec Eng <hgs@...>

There has been discussion on this list/group from time to time about

16 messages 2000/10/20
[#5712] Re: Dynamic languages, SWOT ? — Charles Hixson <charleshixsn@...> 2000/10/20

Hugh Sasse Staff Elec Eng wrote:

[#5882] [RFC] Towards a new synchronisation primitive — hipster <hipster@...4all.nl>

Hello fellow rubyists,

21 messages 2000/10/26

[ruby-talk:5663] Re: local variables (nested, in-block, parameters, etc.)

From: Hugh Sasse Staff Elec Eng <hgs@...>
Date: 2000-10-18 08:48:25 UTC
List: ruby-talk #5663
On Wed, 18 Oct 2000, Yukihiro Matsumoto wrote:

> local.  By the way, what do you think about the for-loop variable,
> which is syntactically block parameter without blocks.
> 
> For example, 
> 
>   index = 345
>   for index in 1..5
>     print "#{index}\n"
>   end
>   print index   # Prints 5
> 
> is almost identical to
> 
>   index = 345
>   (1..5).each do |index|
>     print "#{index}\n"
>   end
>   print index   # Prints 5
> 
> except the former does NOT introduce any block scope.

If this is made clear in the manual -- that *no* new scope is introduced
-- then I'd suggest that present behaviour remain the same.  But the 1.4
manual said:


for

Examples: 

        for i in [1, 2, 3]
          print i*2, "\n"
        end

Syntax: 

        for lhs... in expr [do]
          expr..
        end

Executes body for each element in the result of expression. for is the
syntax sugar for: 

        (expr).each `{' `|' lhs..`|' expr.. `}'


Which rather suggests new scope *is* created...  

I would advocate the simplest (in terms of number of different cases)
rules of scope possible, and that block parameters should have scope
for that block only.  Principle of least to remember? :-)
> 
> 							matz.
> 
	Hugh
	hgs@dmu.ac.uk


In This Thread