[#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
[#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:02535] Default naming for iterator parameters
From:
mrilu <mrilu@...>
Date:
2000-04-20 19:43:45 UTC
List:
ruby-talk #2535
I'm back at my computer after some traveling. I know I think Ruby
subconsiously because today at work (in the midst of java code) I came up
with weird shorthand which could improve code readibility. I've no
idea for syntax "for the other side" but my idea for the caller side
could be presented like this:
{'foo' => 'bar', 'dog' => 'bert'}.each_pair {
print key, ": ", value, "\n"
}
This code is somehow magically translated into following before execution.
{'foo' => 'bar', 'dog' => 'bert'}.each_pair {
|key, value|
print key, ": ", value, "\n"
}
I thought being able to set default iterator parameter naming *might*
be good idea.
Now if people think this is good (I know Matz said at least he's lazy :)
we should think
1) proper default names
2) way to describe default names to interpreter for
home made iterating functions
For the first point the documentation could give a hint, because iterators
are already documented like:
each_key {|key|...}
Iterates over each key in the hash table.
The second is harder, and might require some new syntax.
def each_key
set_default_named_parameters( 'key', 'value' )
# ... normal code with code for iterator
end
Or, logically (and maybe more beautifully):
def weird_iterator(foo) | key, value |
# ... normal code with use of iterator
end
This is just an idea, so I'm not proposing immediate change, nor
do I know how useful default naming would be.