[#5218] Ruby Book Eng tl, ch1 question — Jon Babcock <jon@...>
From: Jon Babcock <jon@kanji.com>
Thanks.
From: Jon Babcock <jon@kanji.com>
Ah, thanks, I think I get it, a slightly different nuance then.
From: Jon Babcock <jon@kanji.com>
'Because all of Ruby has been...' -> 'Because Ruby has been...'?
[#5221] better way to say 'recursive join' — Yasushi Shoji <yashi@...>
in [ruby-dev:6289], Shugo Maeda suggested better name for recursive
[#5240] Ruby for Win32/DOS — Dennis Newbold <dennisn@...>
Not all of us are blessed with the opportunity to be able to develop on
[#5254] problem: undefined method `size' for File — "葡ic Santonacci" <Eric.Santonacci@...>
Hi all,
HI,
[#5264] Re: problem: undefined method `size' for Fil e — Aleksi Niemel<aleksi.niemela@...>
matz critizes good solution argumenting with features lacking from some
[#5268] Proper ConditionVariable usage? — Aleksi Niemel<aleksi.niemela@...>
Abstract
On Wed, 04 Oct 2000 07:05:22 +0900, Aleksi Niemelwrote:
In message <20001004110040.A26666@xs4all.nl>
Hi,
[#5276] Re: Ruby Book Eng tl, ch1 question — schneik@...
[#5310] Errata for Ruby Book? — Jon Babcock <jon@...>
[#5318] Redefining super method as singleton? — Robert Feldt <feldt@...>
On Fri, 6 Oct 2000, Yukihiro Matsumoto wrote:
[#5329] Ruby vs PHP ? — "Valerio Bamberga" <bamberga@...>
Hi!
[#5331] Unit testing network code? — Hugh Sasse Staff Elec Eng <hgs@...>
Can someone give me pointers on how to Unit Test code that is run on
> I think maybe one would test each end on its own first, faking the
[#5335] string streams in Ruby? — Hugh Sasse Staff Elec Eng <hgs@...>
Is there any way, without going through "modifying the internals",
[#5346] Is Ruby "enough better"? — Gabriel Lima <Gabriel.Lima@...>
Hi.
[#5364] Allowing *ary's in the middle of a camma separated list — "Akinori MUSHA" <knu@...>
Hi,
Hi,
At Tue, 10 Oct 2000 14:17:24 +0900,
[#5404] Object.foo, setters and so on — "Hal E. Fulton" <hal9000@...>
OK, here is what I think I know.
At Wed, 11 Oct 2000 11:37:25 +0900,
Hi,
Hi,
Hi,
Hi,
[#5425] Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...>
At Thu, 12 Oct 2000 03:49:46 +0900,
Thanks for the input.
At Thu, 12 Oct 2000 04:53:41 +0900,
At Thu, 12 Oct 2000 07:25:03 +0900,
oops, I didn't read this one before I went out for food..
At Thu, 12 Oct 2000 09:59:19 +0900,
[#5437] Editor recommandations? — "Chris Morris" <chrismo@...>
Any recommendations on editors for Ruby script on Windows?
[#5471] 2 ideas from Haskell — Mark Slagell <ms@...>
Do either of these interest anyone:
[#5479] Some newbye question — Davide Marchignoli <marchign@...>
I am reading the documentation I found about ruby but several points
[#5480] InstallShield version for Ruby soon... — andy@... (Andrew Hunt)
Okay folks,
[#5489] Regexp#matches — Aleksi Niemel<aleksi.niemela@...>
Would someone object aliasing matches for match in Regexp?
[#5505] Sorry, What is Ruby Book — Mansuriatus Shahrir Amir <chioque@...>
Sorry if this information is somewhere obvious. I just stumbled upon
[#5516] Re: Some newbye question — ts <decoux@...>
>>>>> "D" == Davide Marchignoli <marchign@di.unipi.it> writes:
Hi,
On Sat, 14 Oct 2000, Yukihiro Matsumoto wrote:
matz@zetabits.com (Yukihiro Matsumoto) writes:
Dave Thomas <Dave@thomases.com> wrote:
Hi,
> Proposal a and b have incompatibility. I'm not sure it's worth it.
>>>>> "Y" == Yukihiro Matsumoto <matz@zetabits.com> writes:
On Mon, 16 Oct 2000, ts wrote:
>>>>> "Y" == Yukihiro Matsumoto <matz@zetabits.com> writes:
[#5558] GC: malloc_memories — Mathieu Bouchard <matju@...>
Hi,
> |precipitate a new GC cycle if lots of resizing is done. My biggest
[#5570] Notes about GC — Mathieu Bouchard <matju@...>
[#5600] passing single or multiple strings. — Hugh Sasse Staff Elec Eng <hgs@...>
With multple assignments I can get nested arrays "shelled" (like peas)
In message "[ruby-talk:5600] passing single or multiple strings."
[#5603] debug command list in English — "Morris, Chris" <ChrisM@...>
I found this page which lists the interactive debugger commands ... anyone
[#5619] lint? — "Swit" <swit@...>
Is there something like lint for Ruby? I'd like to find NameErrors before
[#5705] Dynamic languages, SWOT ? — Hugh Sasse Staff Elec Eng <hgs@...>
There has been discussion on this list/group from time to time about
Hugh Sasse Staff Elec Eng wrote:
On Sat, 21 Oct 2000, Charles Hixson wrote:
[#5715] Help: sockets broken — jason petrone <jp@...>
I just compiled ruby 1.6.1 on an openbsd 2.6 machine(x86).
[#5716] Re: Array#insert — Aleksi Niemel<aleksi.niemela@...>
> From: jweirich@one.net [mailto:jweirich@one.net]
[#5727] String#slice surprise — "Guy N. Hurst" <gnhurst@...>
Hi,
Dave Thomas wrote:
[#5787] Shells and Ruby — "Dat Nguyen" <thucdat@...>
Hello all,
[#5850] Re: Array#insert rehashed — Aleksi Niemel<aleksi.niemela@...>
Dave asks for:
[#5862] succ but no pred? (& the MURKY award) — "Hal E. Fulton" <hal9000@...>
First of all, a serious question:
[#5873] Integer(String) weirdness for a ruby newbie — Stoned Elipot <Stoned.Elipot@...>
Hi,
[#5881] Q:what about "Programming Ruby"? — Gabriel Lima <Gabriel.Lima@...>
Hi to you all.
[#5882] [RFC] Towards a new synchronisation primitive — hipster <hipster@...4all.nl>
Hello fellow rubyists,
On Fri, 27 Oct 2000, hipster wrote:
[#5947] Hash.new {block} / Hash#default_proc{,_set} — "Brian F. Feldman" <green@...>
I've done very little testing, but I think I've successfully implemented the
[ruby-talk:5293] RE: RFC: Enumerable#every(n)
Hello Musha-san,
> Enumerable#every(n)
>
> Returns an Enumerable object that yields the iterator block for
> every <n> elements. The block is yielded with <n> arguments for
> each, and if the number of elements are short by <n> for the last
> yield, nil's are filled as necessary.
I like the functionality very much. But I have to say I didn't understand
the real semantics when I briefly tried to follow discussion at ruby-dev,
nor when I read the source code (I just got confused, I think your sources
are the normal Ruby source quality, so nothing wrong with them). Then I read
this explanation, and I'm just probably quite tired, but didn't understand
it even then.
Then I remembered the use of arrays in the sources, and the second example
cleared up things. If I may try to describe the functionality it'd be like
this:
Enumerable#every(n)
Returns an Every object, which implements Enumerable interface.
The Every object has an reference to the receiver of this method call,
and <n> specifies the count of elements of original object to be grouped.
Every#each
Iterates through the referenced object by calling it's method each and
gathering elements. After <n> elements gathered in an array it yields
the array to the associated iterator block.
If the last group doesn't get filled from original's enumeration,
it's padded with nils.
Thus Every#each regroups original Enumerable#each results.
Example: every = ["1", "a", "2", "b", "3"].every(2)
p every
every.each {|ary| p ary}
Outputs: #<Every:0xa06cbd8>
["1", "a"]
["2", "b"]
["3", nil]
As all methods defined in the module Enumerable rely on method each
which the class have to provide, everything in Enumerable is applicable
to an Every object.
Example: # print first grouping which first element
# contains some text
ary = ["1", "a", "2", "b", "3"]
p ary.every(3).find {|ary| ary[0] =~ /\w+/ }
Outputs: ["b", "3", nil]
> 1) Is the name "every" appropriate?
I think Every, and methods, would be better named as Group. Thus leading to
$ ruby -e 'p (("A".."Z").group(4).find_all{|i| ...
> 2) Is it worth being integrated to the standard Enumerable class?
Can't say for sure. I think it is, as there are some happy side-effects if
it's redefined. Someone remembers a ruby-talk thread where we discussed how
to gather all the output of an iterator into an array. Well, provided we
know how much we should get we could say
obj.group(this_many).each {|ary_of_all_elements_gathered| ... }
Of course we could improve this. As there's already Enumerable#to_a we can
say the above example better as
all_elements = obj.group(this_many).to_a
If there's a way to express we want the Group object gather everything it
would be even simpler
all_elements = obj.group.to_a # def group(n=nil)
And for convenience we would probably get
all_elements = obj.suck_until_theres_nothing_but_an_array_in_the_end
Anyway, the trick to get Every work like this is to be able to pass
every_each_i wrapped into a proc, which could then be associated with a
method. Or maybe the Proc or Method which should be collected could be
provided to Every object.
def get_ten_random_numbers
10.times { yield rand; }
end
nums_in_5_groups = Every.new(5, self.method("get_ten_random_numbers"))
This side note is no real proposition, just a reminder that there has been
need for something like this earlier; then they just didn't realize they'd
get something better :).
Even in current form I'd welcome this new functionality, as it's no massive
overkill, just a small creature which does just one thing and does it well.
- Aleksi