[#927] UnboundMethod#to_proc — Dave Thomas <dave@...>
I'm wondering what I can do with a Proc generated by
17 messages
2003/04/06
[#929] Re: UnboundMethod#to_proc
— "Chris Pine" <nemo@...>
2003/04/06
----- Original Message -----
[#934] Re: UnboundMethod#to_proc
— Mathieu Bouchard <matju@...>
2003/04/06
[#940] Re: UnboundMethod#to_proc
— chr_news@...
2003/04/07
>
[#941] Re: UnboundMethod#to_proc
— Dave Thomas <dave@...>
2003/04/07
>> If they have diverging interfaces such that the contracts conflict
[#936] docs on implementation of ruby and/or ruby-gc ? — Ruben Vandeginste <Ruben.Vandeginste@...>
4 messages
2003/04/07
[#964] Range in logical context — Dave Thomas <dave@...>
If I run
7 messages
2003/04/16
[#965] Re: Range in logical context
— Mauricio Fern疣dez <batsman.geo@...>
2003/04/16
On Thu, Apr 17, 2003 at 06:10:40AM +0900, Dave Thomas wrote:
[#973] problem with rb_rescue2() ? — Mathieu Bouchard <matju@...>
5 messages
2003/04/19
Re: Is this an intended change in string interpolation
From:
matz@... (Yukihiro Matsumoto)
Date:
2003-04-08 05:17:16 UTC
List:
ruby-core #949
Hi,
In message "Is this an intended change in string interpolation"
on 03/04/08, Dave Thomas <dave@thomases.com> writes:
|In the latest CVS:
|
|irb(main):002:0> /c(a)t/ =~ "cat"
|=> 0
|irb(main):003:0> "d#$1ve"
|=> "d"
|
|In older Rubies, the #$1 sequence was interpolated without swallowing
|the rest of the string.
|
|Also now I can create globals such as
|
|irb(main):004:0> $1ve = "cat"
|=> "cat"
|irb(main):005:0> "d#$1ve"
|=> "dcat"
|
|Cool feature, or wee bug? :)
From CVS history, I allowed variables like "$1ve" on 2000-04-10. The
problem is I completely forget the reason why I did allow "$1ve". But
later, I explicitly disallow variables like "@1ve". So, for the
consistency, I should disallow "$1ve" as well.
OK, I will change the behavior to:
/c(a)t/ =~ "cat"
=> 0
"d#$1ve"
=> "dave"
$1ve = "cat"
-:1: syntax error
$1ve = "cat"
^
Thank you for pointing out inconsistency.
matz.