[#2332] Ruby-Python fusion? — mrilu <mrilu@...>
Usually I give some time for news to settle before I pass the word, but
7 messages
2000/04/01
[#2353] Re: Function of Array.filter surprises me — schneik@...
5 messages
2000/04/03
[#2361] crontab — Hugh Sasse Staff Elec Eng <hgs@...>
I want to have a program that may be run between certain times.
11 messages
2000/04/05
[#2375] Marshal: Want string out, but want depth specified? — Hugh Sasse Staff Elec Eng <hgs@...>
@encoded = [Marshal.dump(@decoded, , depth)].pack("m")
7 messages
2000/04/07
[#2378] Re: Marshal: Want string out, but want depth specified?
— matz@... (Yukihiro Matsumoto)
2000/04/07
Hi,
[#2376] Iterator into array — Dave Thomas <Dave@...>
15 messages
2000/04/07
[#2397] Could missing 'end' be reported better? — mrilu <mrilu@...>
I'm not sure one could easily parse, or moreover report, this error better.
5 messages
2000/04/08
[#2404] Re: Iterator into array — Andrew Hunt <andy@...>
>It's still possible to introduce a new syntax for collecting yielded
6 messages
2000/04/08
[#2412] Re: Could missing 'end' be reported better? — h.fulton@...
7 messages
2000/04/09
[#2414] Re: Could missing 'end' be reported better?
— matz@... (Yukihiro Matsumoto)
2000/04/09
Hi,
[#2429] Please join me, I'm Hashing documentation — mrilu <mrilu@...>
This is a story about my hashing ventures, try to bear with me.
5 messages
2000/04/10
[#2459] Precedence question — Dave Thomas <Dave@...>
7 messages
2000/04/12
[#2474] Ruby 1.4.4 — Yukihiro Matsumoto <matz@...>
Ruby 1.4.4 is out, check out:
5 messages
2000/04/14
[#2494] ANNOUNCE : PL/Ruby — ts <decoux@...>
7 messages
2000/04/17
[#2495] Re: 'in' vs. 'into' — Andrew Hunt <andy@...>
># rescue MyException into myVar
4 messages
2000/04/17
[#2514] frozen behavior — Andrew Hunt <Andy@...>
7 messages
2000/04/19
[#2530] Re: 'in' vs. 'into' — Andrew Hunt <andy@...>
>Hmm, I've not decided yet. Here's the list of options:
6 messages
2000/04/20
[#2535] Default naming for iterator parameters — mrilu <mrilu@...>
I'm back at my computer after some traveling. I know I think Ruby
5 messages
2000/04/20
[#2598] different thread semantics 1.4.3 -> 1.4.4 — hipster <hipster@...4all.nl>
Hi fellow rubies,
4 messages
2000/04/28
[ruby-talk:02534] Re: 'in' vs. 'into'
From:
schneik@...
Date:
2000-04-20 16:12:24 UTC
List:
ruby-talk #2534
Matz writes: # In message "[ruby-talk:02495] Re: 'in' vs. 'into'" # on 00/04/17, Andrew Hunt <andy@Toolshed.Com> writes: # | # | ># rescue MyException into myVar # | ># # | >I agree. # | # |I like "into" as well, for what it's worth. # # Hmm, I've not decided yet. Here's the list of options: # # * rescue IOError in var # # Current parser accepts this syntax. No new reserved word # introduced. # # * rescue IOError into var # # More descriptive than 'in'. Introducing new reserved word, which # raise backward compatibility problem. For the time being, I vote for this one, although I think Dave's first suggestion might be a good choice (but I haven't had time to think about it). # * rescue IOError => var # # No reserved word introduced. Symbols may ambiguous. # # * exception # # This option introcudes new global function `exception' which # returns the $! value. No reserved word introduced. I think this # simple way. What happens if you have recoverable exceptions in exception handlers spread across multiple modules written by different people? Would you be able to rely on "$!"? (Would the very first thing that you would need to do is make a local copy of "$!"?) # * Exception::last # # This may more descriptive than mere `exception'. But I feel it's # too long to type in. You know I'm lazy. Notice `ruby' is 2 # letter shorter than `python'? Conrad Schneiker (This note is unofficial and subject to improvement without notice.)