[#16113] Strange idea... exporting from a scope — "Hal E. Fulton" <hal9000@...>

Hello...

33 messages 2001/06/01

[#16364] Re: Garbage Collection? — Michael Davis <mdavis@...>

Windows 2000 and linux (RedHat 6.2). I have run these tests on both OSs.

12 messages 2001/06/09

[#16400] Symbolic Computation III — Mathieu Bouchard <matju@...>

14 messages 2001/06/11

[#16502] Playing with Ruby Syntax (was: Initial thoughts about Ruby From a Smalltalk Programmer) — jweirich@...

Michael> Hi Everyone, I have to say I'm utterly fascinated by Ruby

9 messages 2001/06/15

[#16661] Problem running irb with Ruby 1.6.4 under FreeBSD 4.0 — Bob Alexander <balexander@...>

I've installed Ruby 1.6.4 on a FreeBSD 4.0 machine, and get the

11 messages 2001/06/20

[#16686] opening db files made by apache dbmmanage — Fritz Heinrichmeyer <fritz.heinrichmeyer@...>

14 messages 2001/06/21

[#16801] rb_define_class() vs Class.new() — Kero van Gelder <kero@...4050.upc-d.chello.nl>

Hi,

18 messages 2001/06/23
[#16802] Re: rb_define_class() vs Class.new() — ts <decoux@...> 2001/06/23

>>>>> "K" == Kero van Gelder <kero@d4050.upc-d.chello.nl> writes:

[#16841] RE: national characters is strings — "Aleksei Guzev" <aleksei.guzev@...>

Next week I'll try to rebuild Ruby with Unicode strings. But it would be

15 messages 2001/06/25
[#16842] Re: national characters is strings — matz@... (Yukihiro Matsumoto) 2001/06/25

Hi,

[#16843] Re: national characters is strings — "Aleksei Guzev" <aleksei.guzev@...> 2001/06/25

That's good enough. But I'm afraid this could ( not would ) cause string

[#16868] Something strange with Ruby's inheritance mechanism — Eric Jacoboni <jaco@...>

As Ruby beginner, i try some "canonical" OO scripts. Doing so, I've

14 messages 2001/06/25
[#16873] RE: Something strange with Ruby's inheritance mechanism — "Aleksei Guzev" <aleksei.guzev@...> 2001/06/26

[#16879] Re: Something strange with Ruby's inheritance mechanism — Mathieu Bouchard <matju@...> 2001/06/26

On Tue, 26 Jun 2001, Aleksei Guzev wrote:

[#16869] Something strange with Ruby's inheritance mechanism — Eric Jacoboni <jaco@...>

As Ruby beginner, i try some "canonical" OO scripts. Doing so, I've

12 messages 2001/06/25

[#16881] — "Aleksei Guzev" <aleksei.guzev@...>

32 messages 2001/06/26
[#16916] Re: Method overloading (option) Was: Re: — "Wayne Blair" <wayne.blair@...> 2001/06/26

[#16920] Re: Method overloading (option) Was: Re: — matz@... (Yukihiro Matsumoto) 2001/06/26

Hi,

[#16888] finalizers, destructors and whatnot — "David Leal" <david@...>

Hi all,

16 messages 2001/06/26

[#17037] keeping an Exception object alive — David Alan Black <dblack@...>

Hello --

19 messages 2001/06/28
[#17055] Re: keeping an Exception object alive — matz@... (Yukihiro Matsumoto) 2001/06/29

Hi,

[#17066] RCR: Exception methods (was: Re: Re: keeping an Exception object alive) — David Alan Black <dblack@...> 2001/06/29

Hello --

[#17076] Re: RCR: Exception methods (was: Re: Re: keeping an Exception object alive) — matz@... (Yukihiro Matsumoto) 2001/06/29

Hi,

[#17079] Re: RCR: Exception methods (was: Re: Re: keeping an Exception object alive) — David Alan Black <dblack@...> 2001/06/29

Hello --

[#17138] Re: RCR: Exception methods (was: Re: Re: keeping an Exception object alive) — matz@... (Yukihiro Matsumoto) 2001/07/02

Hi,

[#17141] Re: RCR: Exception methods (was: Re: Re: keeping an Exception object alive) — David Alan Black <dblack@...> 2001/07/02

Hello --

[#17142] Re: RCR: Exception methods (was: Re: Re: keeping an Exception object alive) — ts <decoux@...> 2001/07/02

>>>>> "D" == David Alan Black <dblack@candle.superlink.net> writes:

[ruby-talk:16135] Re: Block arguments vs method arguments

From: Chris Moline <ugly-daemon@...>
Date: 2001-06-01 11:52:16 UTC
List: ruby-talk #16135
On Fri, Jun 01, 2001 at 06:19:54AM +0900, Sean Russell wrote:
> 1) There are better (IMHO) solutions for the problem.  I, personally, liked 
> the earlier suggestion of defining scope with { |:var| ... }, and I'm not 
> sure whatever happened to this recommendation.
I don't like either : or < >. Someone here made the suggestion that we use ( )
instead of | | and make them to mean that its local to the block. I like this
proposal as it makes things more consistent IMO. 

> 3) An argument for ':var' over '<var>' can be made in recognizing that:
> 	my_proc { |  var1, :var2 | }
> is more flexible than
> 	my_proc { < var1, var2 > }
> I shudder to imagine that attempts to solve this might lead to declarations 
> such as:
> 	my_proc { < var1 > | var2 | }
If I remember right the var1 would behave as it does now while the :var2 would
be local. Am I right?? Why not just change | | to ( ) and then if you need to 
change a var just do

reciever.method do( arg )
	var_in_scope = arg
end

> I agree with the philosophy of keeping maximum backwards compatibility, but I 
> think that in some cases it is much better lose backwards compatibility for 
> the sake of clean syntax.  I don't think that "<...>" is powerful enough to 
> sufficiently solve the scoping "issue", and that using it is a contract for a 
> further syntactic change.
I don't agree overly much with backwards compatibility. I can undestand why
people want it but it seems to me that it hampers development and progress and
that eventually the language becomes ugly. I think we need to find a better way
of supporting backwards compatibility. Perhaps some kind of built in translation
ability?? ( just an idea ). 
> 
> 4) '<' and '>' are sharp, pointy glyphs, denoting hard, angry imagery; they 
> are unfriendly characters, and someone could get hurt using them.  Studies 
> show that people who overuse '<' and '>' are more prone to violence than 
> those who don't;  this is supported up by the fact that there are very few 
> incidences of workplace violence in Lisp-shops. (Ahem...)
lol

Sincerly,
Chris Moline

In This Thread