[#955] Ruby 1.4.3 — Yukihiro Matsumoto <matz@...>
Ruby 1.4.3 is out, check out:
1 message
1999/12/07
[#961] Ruby compileable by C++ compiler? — Clemens Hintze <c.hintze@...>
Hi,
8 messages
1999/12/10
[#962] Re: Ruby compileable by C++ compiler?
— matz@... (Yukihiro Matsumoto)
1999/12/10
Hi,
[#963] Re: Ruby compileable by C++ compiler?
— Clemens Hintze <clemens.hintze@...>
1999/12/10
Wei,
[#964] Bastion or SecurityManager for Ruby? — Clemens Hintze <clemens.hintze@...>
Hi,
15 messages
1999/12/10
[#966] Re: Bastion or SecurityManager for Ruby?
— nakajima kengo<ringo@...>
1999/12/10
Hello Clemens,
[#967] Re: Bastion or SecurityManager for Ruby?
— matz@... (Yukihiro Matsumoto)
1999/12/10
Hi,
[#989] a question about to_i — Friedrich Dominicus <Friedrich.Dominicus@...>
Sorry, I'm quite new to ruby. But I encounterd the following problem. If
17 messages
1999/12/19
[ruby-talk:01017] Re: Blocks, Procs, and iterators
From:
matz@... (Yukihiro Matsumoto)
Date:
1999-12-31 16:04:00 UTC
List:
ruby-talk #1017
Happy new year.
Yes, we already had a new year.
In message "[ruby-talk:01014] Blocks, Procs, and iterators"
on 99/12/31, Clemens Hintze <c.hintze@gmx.net> writes:
|AFAIK --if I have understood matz right-- there is only a performance
|penalty by using your second example.
I forgot to mention one big difference. You can't swap self with
instance_eval() as in [ruby-talk:01010] by using yield. &block is the
only way to pass blocks around directly.
You can use {|x| yield x} trick for most of the cases, but not for the
instance_eval() case.
|BTW: Best wishes for 2000 to all of the Ruby community and you
|families & friends & ... :-)))
I strongly hope the Ruby book in English will be published this year.
matz.