[#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: Regexp quoting (again)
From:
Austin Ziegler <austin@...>
Date:
2003-04-17 16:49:42 UTC
List:
ruby-core #972
On Thu, 17 Apr 2003 22:12:59 +0900, Dave Thomas wrote: > I know this has been discussed at length, but could I put in a > vote not to warn on /]/. I now have a lot of legacy code that > generates warnings, and for the life of me I can't see a good > reason for it. It's a bit like generating warnings for characters > inside strings: > > "1) Break 3 eggs in a bowl" > > recipe:1 warning - unmatched closing parenthesis in string > > The ']' in a regexp is a terminator, and is not otherwise special. > Why should it need to be escaped? I agree. vim recognises a bare ] properly, and I do a lot of my regexp testing in vim (perhaps not a good idea, but...). vim, in fact, recognises /[/, /[]/, and /]/ as valid character searches. /[]]/ is the same as /]/ or /[\]]/. I'm not sure how hard this would be, but aside from /[]]/, I don't think that any of these would/should be problematic. -austin -- Austin Ziegler, austin@halostatue.ca on 2003.04.17 at 12:20:08