[#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:5549] Re: Some newbye question

From: Mark Slagell <mslagell@...>
Date: 2000-10-15 15:27:04 UTC
List: ruby-talk #5549
ts wrote:
> 
> >>>>> "D" == Dave Thomas <Dave@thomases.com> writes:
> 
> D>     iterate { <i, j> ...  }     # 'i' is always block local
> 
>  I prefer this rather than the original proposition (1)
> 
> Guy Decoux

As Dave says, params are really placeholders; they behave as pronouns as
opposed to nouns, and we all know that in everyday language, pronouns
carry an assumption of local scope.  To say "whenever I get a personal
letter, I open it" introduces no ambiguity about "it" - we don't have to
worry what the word means at other points in a larger conversation, and
the sentence can be grasped and reasoned about in isolation.  Removing
that assurance in a programming language context, esp. with iterators
("for each thing in this set, do such and such with it"), makes it
harder to be confident about unintended side effects, so that you have
to keep track of what parameter names have been used when you start
nesting procs.

So I guess what I'm saying is that I'd encourage making block params
local.  On the other hand I don't have a lot of old code that it would
break.  If <> and || were given these different scope meanings, it would
be okay too, I'd just use <> all the time. :-)

  Mark

In This Thread