[#17055] Set#map! vs. map — "David A. Black" <dblack@...>
Hi --
Hi,
At Tue, 3 Jun 2008 10:13:07 +0900,
At Tue, 3 Jun 2008 13:39:10 +0900,
Hi --
At Tue, 3 Jun 2008 18:03:23 +0900,
[#17067] Eval'ing 'yield' in 1.8 and 1.9 — "Vladimir Sizikov" <vsizikov@...>
Hi,
Hi,
[#17069] Ruby on zLinux — "Eric K. Dickinson" <eric.dickinson@...>
I posted this on the Ruby-Talk list with no success.
[#17084] Enumerable::Enumerator#with_memo — "Akinori MUSHA" <knu@...>
Hi,
Akinori MUSHA wrote:
Akinori MUSHA wrote:
On Mon, Jun 9, 2008 at 12:11 PM, David Flanagan <david@davidflanagan.com> wrote:
On Mon, Jun 9, 2008 at 10:57 PM, Jeremy Kemper <jeremy@bitsweat.net> wrote:
Martin DeMello wrote:
On Tue, Jun 10, 2008 at 10:04 AM, David Flanagan
David Flanagan wrote:
[#17092] Iconv#iconv(str, start, length) doesn't really convert str[start, length] — Vincent <vincentlu@...>
Hi Core,
Hi Core,
Hi,
[#17106] r16747: This commit and comment are real? — "Luis Lavena" <luislavena@...>
Checking a feed of the changes in ruby repository found this:
On Wed, Jun 4, 2008 at 7:21 PM, Luis Lavena <luislavena@gmail.com> wrote:
[#17116] Standardizing RUBY_PLATFORM — Brian Ford <brixen@...>
Hi all,
On Jun 4, 8:52=A0pm, Brian Ford <bri...@gmail.com> wrote:
[#17126] remove ObjectSpace.each_object from test/unit — Tanaka Akira <akr@...>
I wrote a patch to remove ObjectSpace.each_object from test/unit.
[#17155] lambda { break } — ts <decoux@...>
Hi,
[#17161] Ruby 1.8.7-p17 has been released — "Akinori MUSHA" <knu@...>
Folks,
[#17162] Release Plan: Ruby 1.9.0-2 — SASADA Koichi <ko1@...>
Hi,
Hi,
Hi,
Hi,
Kouhei Sutou <kou@cozmixng.org> writes:
I have to agree, on the documentation side.
SASADA Koichi wrote:
[#17167] Mail count in Subject — "Dirk Traulsen" <dirk.traulsen@...>
Hi!
All,
Warren Brown wrote:
At 11:54 08/06/10, Urabe Shyouhei wrote:
On Tue, Jun 10, 2008 at 4:54 AM, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
Luis Lavena wrote:
[#17186] REXML Separation — Federico Builes <federico.builes@...>
Hello,
[#17261] [Ruby 1.9 - Bug #161] (Open) Profile library seems broken in 1.9 15427cat t.rv — Dave Thomas <redmine@...>
Issue #161 has been reported by Dave Thomas.
[#17272] [Ruby 1.9 - Bug #167] (Open) net/telnet login() method no longer works under 1.9 — Dave Thomas <redmine@...>
Issue #167 has been reported by Dave Thomas.
On Jun 15, 2008, at 11:25 PM, Dave Thomas wrote:
Yes, indeed it does...
[#17283] Major change in 1.8.6: convert_type now uses private conversion methods too — "Vladimir Sizikov" <vsizikov@...>
Hi,
Vladimir Sizikov wrote:
Hi,
[#17291] miniruby dependencies broken in 1.9 — Ryan Davis <ryand-ruby@...>
I've been having builds break with -j 4. This should add $(PREP) to
Hi,
[#17293] [Ruby 1.8 - Bug #175] (Open) Rational#power2 raises a NameError or causes infinite loops when passed a Rational — Arthur Schreiber <redmine@...>
Issue #175 has been reported by Arthur Schreiber.
[#17310] [Ruby 1.9 - Bug #178] (Open) File.open on sprintf-formatted string fails with encoding conversion error on OS X — Eric Hodel <redmine@...>
Issue #178 has been reported by Eric Hodel.
Issue #178 has been updated by Yui NARUSE.
[#17327] A plea for a release process — Brian Ford <brixen@...>
Hi all,
Hello,
On Jun 18, 1:12=A0pm, "U.Nakamura" <u...@garbagecollect.jp> wrote:
[#17345] Understanding the output of Kernel#caller — "Wilson Bilkovich" <wilsonb@...>
I am trying to understand what Ruby 1.8 outputs when "caller" is invoked.
[#17353] patches for tests of rubygems — "Yusuke ENDOH" <mame@...>
Hi,
Hi,
On Jun 24, 2008, at 05:55 AM, Yusuke ENDOH wrote:
On Jun 25, 2008, at 11:21 AM, Eric Hodel wrote:
[#17356] A faster Array#delete — Daniel Berger <djberg96@...>
Hi all,
[#17377] Re: Ruby 1.9.0/1.8.7/1.8.6/1.8.5 new releases (Security Fix) — "Bill Kelly" <billk@...>
Hi,
[#17392] XMLRPC socket patch — Dario Meloni <mellon85@...>
Hi,
[#17393] URGENT: Possible fixes for segfaults and vulnerabilities available for review in ruby-talk — "Igal Koshevoy" <igal@...>
All currently available versions of MRI Ruby are either vulnerable to
Sorry for a late reply but I think I've fixed this issue. Can someone
Urabe Shyouhei wrote:
Igal Koshevoy wrote:
Urabe Shyouhei wrote:
Igal Koshevoy wrote:
Urabe Shyouhei wrote:
Hello, I think current 1.8.6/1.8.7 is stable than p230/p22, so I decided
On Wed, Jul 2, 2008 at 12:41 PM, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
Hello,
Hi Urabe,
Vladimir Sizikov wrote:
Charles Oliver Nutter wrote:
Urabe Shyouhei wrote:
Igal Koshevoy wrote:
Charles Oliver Nutter wrote:
On 7/3/08, Igal Koshevoy <igal@pragmaticraft.com> wrote:
Wilson Bilkovich wrote:
Charles Oliver Nutter wrote:
On 02/07/2008, Charles Oliver Nutter <charles.nutter@sun.com> wrote:
In article <a5d587fb0807160533r4534fabdg257b4a9523b15f1e@mail.gmail.com>,
On Sat, Jul 19, 2008 at 02:18:05PM +0900, Federico Builes wrote:
On Sun, Jul 20, 2008 at 12:43:46AM +0900, Federico Builes wrote:
When will we see a new 1.8.6 release?
Hi,
Hi,
On Fri, Jul 25, 2008 at 02:04:15AM +0900, Vladimir Sizikov wrote:
On Fri, Jul 25, 2008 at 04:35:43AM +0900, Jeremy Henty wrote:
Jeremy,
Hi,
On Thu, Jul 24, 2008 at 9:19 PM, Nobuyoshi Nakada <nobu@ruby-lang.org>
Hi,
Hi,
When can we expect a release?
Hi Vladimir, hi Urabe,
Thank you, I merged this revision into 1.8.7.
Hi,
In article <48662E99.7030508@pragmaticraft.com>,
Federico Builes wrote:
Igal Koshevoy wrote:
M. Edward (Ed) Borasky wrote:
Igal Koshevoy wrote:
Igal Koshevoy wrote:
Tanaka Akira wrote:
In article <48678E3D.8020602@pragmaticraft.com>,
Tanaka Akira wrote:
In article <4867A6AC.4060902@pragmaticraft.com>,
[#17412] Time for a release management committee? — Charles Oliver Nutter <charles.nutter@...>
It seems like recent problems with patchlevel and minor 1.8 releases
[#17427] 1.8 release management — Yukihiro Matsumoto <matz@...>
Hi,
On Sun, Jun 29, 2008 at 06:06:14PM +0900, Yukihiro Matsumoto wrote:
Hi,
Let me describe some simple questions about Ruby 1.8.6 that are not
For what I know,
On 6/30/08, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
Wilson Bilkovich wrote:
On Thu, Jul 3, 2008 at 4:41 PM, Igal Koshevoy <igal@pragmaticraft.com> wrote:
Luis Lavena wrote:
Urabe Shyouhei wrote:
Igal Koshevoy wrote:
Urabe Shyouhei wrote:
Hi,
Vladimir Sizikov wrote:
On Fri, Jul 4, 2008 at 10:49 PM, Igal Koshevoy <igal@pragmaticraft.com> wrote:
[ruby-core:17356] A faster Array#delete
Hi all,
Windows XP
VC++ 8
I noticed that the Array#delete method in array.c is basically copying
the existing array element by element into a new array object. I
suspected it could be improved so I tried this.
Using an approach similar to Array#delete_at, I came up with this:
VALUE rb_ary_delete(VALUE self, VALUE v_object){
long i, n, length;
int modified = 0;
VALUE v_return = Qnil;
length = RARRAY(self)->len;
for(i = 0; i < RARRAY(self)->len; i++){
if(rb_equal(v_object, RARRAY(self)->ptr[i])){
if(!modified){
rb_ary_modify(self);
modified = 1;
}
for(n = 0; n < length; n++)
RARRAY(self)->ptr[n-1] = RARRAY(self)->ptr[n];
length -= 1;
RARRAY(self)->len = length;
i -= 1;
}
}
/* If there was no match found and block was provided,
* return the value of the yielded block. Otherwise, return
* the deleted value.
*/
if((!modified) && (rb_block_given_p())){
v_return = rb_yield(rb_block_proc());
}
else{
if(modified)
v_return = v_object;
}
return v_return;
}
Then I ran this benchmark:
require 'benchmark'
MAX = 30000
array = ['daniel'] * 1000
array << ['charles'] * 1000
array << ['matz'] * 1000
array << ['larry'] * 1000
array << ['guido'] * 1000
array.flatten!
Benchmark.bm(10) do |x|
x.report("delete"){
MAX.times{ array.delete('larry') }
}
end
Old Array#delete:
user system total real
delete 13.125000 0.000000 13.125000 ( 13.468000)
New Array#delete:
user system total real
delete 3.704000 0.000000 3.704000 ( 3.781000)
So, about a 3x speed increase in my tests, where I compiled both
versions with MS VC++ 8 on Windows XP.
I thought I would see a substantial memory usage decrease, but my
(limited) testing didn't show more than an 8k decrease for the Ruby process.
The only test I could break was an unrelated Array#collect! test:
# With the change, it returns [3,3]
def test_collect_bang_removes_elements_before_they_are_reached
a = [1,2,3]
assert_equal([2, 3], a.collect!{ |e| a.delete(a[1]) })
end
However, I believe the semantics for modifying an array in-place in the
middle of a collect block are undefined, so I'm not sure the test I came
up with is actually valid.
Thoughts? Suggestions? Comments?
Thanks,
Dan