[#12073] Re: Ruby is much slower on linux when compiled with --enable-pthread? — "M. Edward (Ed) Borasky" <znmeb@...>
-----BEGIN PGP SIGNED MESSAGE-----
M. Edward (Ed) Borasky wrote:
On Wed, Sep 05, 2007 at 08:24:57PM +0900, Florian Frank wrote:
On 9/5/07, Sam Roberts <sroberts@uniserve.com> wrote:
[#12085] New array methods cycle, choice, shuffle (plus bug in cycle) — David Flanagan <david@...>
Four new methods have been added to Array the Ruby 1.9 trunk. I've got
On 9/6/07, David Flanagan <david@davidflanagan.com> wrote:
Wilson Bilkovich wrote:
On 9/7/07, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
David Flanagan <david@davidflanagan.com> writes:
On 9/13/07, Christian Neukirchen <chneukirchen@gmail.com> wrote:
Nikolai Weibull wrote:
Restarting this thread because I missed it the first time around and
Hi,
On Thu, Jul 31, 2008 at 7:50 PM, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
Gregory Brown wrote:
Michael Neumann wrote:
Hi --
On 8/1/08, David A. Black <dblack@rubypal.com> wrote:
Wilson Bilkovich wrote:
Hi,
Hi --
2008/8/2 Yukihiro Matsumoto <matz@ruby-lang.org>:
Hi,
Yukihiro Matsumoto wrote:
Florian Frank wrote:
Hi,
On Sun, Aug 3, 2008 at 9:37 AM, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
On Jul 31, 2008, at 7:33 PM, Charles Oliver Nutter wrote:
Jim Weirich wrote:
On Aug 1, 2008, at 1:53 PM, Thomas Enebo wrote:
On Fri, Aug 1, 2008 at 2:01 PM, Jim Weirich <jim.weirich@gmail.com> wrote:
Gregory Brown wrote:
On Aug 1, 2008, at 2:40 PM, Thomas Enebo wrote:
[#12096] Next 1.8.6 on Sept. 22 — Urabe Shyouhei <shyouhei@...>
Hi all.
Well there is this patch:
Rocky Bernstein wrote:
-----BEGIN PGP SIGNED MESSAGE-----
On 9/10/07, M. Edward (Ed) Borasky <znmeb@cesmail.net> wrote:
On Sunday 09 September 2007, Urabe Shyouhei wrote:
[#12118] Is this expected behavior? — James Edward Gray II <james@...>
As part of TextMate's development process we have an application on a
[#12140] Strange ripper bug — "Alexey I. Froloff" <sir_raorn@...>
Sometimes, ripper can't parse valid code (trunk from yesterday).
On [Wed, 12.09.2007 03:05], Alexey I. Froloff wrote:
On [Thu, 13.09.2007 02:58], Kirill A. Shutemov wrote:
Hi,
[#12143] Blocks passed to constructors - is this behavior by design? — "John Lam (CLR)" <jflam@...>
class Foo
It's because the constructor isn't actually finished executing, and the
[#12166] Wrapped loads and Module::nesting — David Flanagan <david@...>
When I call load with a second argument of true, the file is loaded into
[#12184] Misleading error message with URI::InvalidURIError — "Douglas Tan" <bianster@...>
The error message that URI.parse displays when supplied with a uri
[#12200] class variables and singleton classes — Eric Hodel <drbrain@...7.net>
Class variables in singleton classes are separate from class
[#12201] how about actors implemented in ruby-core itself — hemant <gethemant@...>
Hi,
On 9/20/07, hemant <gethemant@gmail.com> wrote:
Hi,
[#12220] `ri Kernel#open` Bug — James Edward Gray II <james@...>
$ ri -T Kernel#open
On Sep 21, 2007, at 16:42, James Edward Gray II wrote:
On Sep 21, 2007, at 8:13 PM, Eric Hodel wrote:
On Sep 22, 2007, at 7:28 AM, Jim Freeze wrote:
[#12231] Wrong return value with []= — Michael Neumann <mneumann@...>
Hi,
[#12237] Latest benchmarks — "M. Edward (Ed) Borasky" <znmeb@...>
I just ran the benchmark suite that comes with Ruby 1.9 on my 32-bit
[#12247] Fibers as semi-coroutines enabled by default — David Flanagan <david@...>
Hi all,
Hi,
[#12248] arbitrary Unicode characters in identifiers? — David Flanagan <david@...>
[#12255] Array#-, &, |, uniq don't use == — murphy <murphy@...>
Hello!
[#12284] gc.c -- possible logic error? — Hugh Sasse <hgs@...>
I've been looking at Tom Copeland's memory allocation problem:
On Fri, 28 Sep 2007 21:57:22 +0900, Hugh Sasse <hgs@dmu.ac.uk> wrote:
On Sat, 29 Sep 2007, MenTaLguY wrote:
In article <Pine.GSO.4.64.0709281302390.26570@brains.eng.cse.dmu.ac.uk>,
On Tue, 2 Oct 2007, Tanaka Akira wrote:
In article <Pine.GSO.4.64.0710011802250.11425@brains.eng.cse.dmu.ac.uk>,
On Tue, 2 Oct 2007, Tanaka Akira wrote:
On Oct 1, 2007, at 10:54 , Hugh Sasse wrote:
On Tue, 2 Oct 2007, Eric Hodel wrote:
[#12294] String.force_encoding — David Flanagan <david@...>
Hi,
[#12305] Will 1.8.6 remain compiled with VC6? — "Luis Lavena" <luislavena@...>
Hello Core developers.
On 9/30/07, Luis Lavena <luislavena@gmail.com> wrote:
On 9/30/07, Austin Ziegler <halostatue@gmail.com> wrote:
On 9/30/07, Luis Lavena <luislavena@gmail.com> wrote:
On 9/30/07, Austin Ziegler <halostatue@gmail.com> wrote:
I know this not the right place to post this, but I'll start here
Austin Ziegler wrote:
> Yes, let's take this to Ruby-Talk so we can all participate. Most of the
On 9/30/07, Charlie Savage <cfis@savagexi.com> wrote:
On 01/10/2007, Charlie Savage <cfis@savagexi.com> wrote:
On 10/3/07, Michal Suchanek <hramrach@centrum.cz> wrote:
Re: Bug in BigDecimal#round ?
On 9/27/07, Jano Svitok <jan.svitok@gmail.com> wrote:
> On 9/27/07, Ryan Platte <ryan.platte@gmail.com> wrote:
> > A coworker discovered some disturbing behavior in BigDecimal#round.
> > The output I get from the program below is:
> >
> > ===== begin output
> >
> > These values appended to '0.0000' cause BigDecimal#round to return
> > nonzero:
> > [5, 6, 7, 8, 9, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62,
> > 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79,
> > 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96,
> > 97, 98, 99]
> >
> > These numbers of zeroes between the decimal point and a 7 cause
> > BigDecimal#round to return nonzero:
> > [4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64, 68, 72,
> > 76, 80, 84, 88, 92, 96, 100]
> >
> > ===== end output
> >
> > ===== begin code
> >
> > require 'bigdecimal'
> >
> > vary_number_after_four_zeroes = (1..100).map { |i|
> > bd = BigDecimal.new("0.0000#{i}"); [i, bd.round.to_s]
> > }
> > seed_values_triggering_misbehavior_with_four_zeroes =
> > vary_number_after_four_zeroes.reject {|i, bds| bds == '0.0'}.map {|
> > i, bds| i}
> >
> > vary_number_of_zeroes = (1..100).map { |i|
> > bd = BigDecimal.new("0.#{'0' * i}7"); [i, bd.round.to_s]
> > }
> > number_of_zeroes_triggering_misbehavior =
> > vary_number_of_zeroes.reject {|i, bds| bds == '0.0'}.map {|i, bds|
> > i}
> >
> > puts "These values appended to '0.0000' cause BigDecimal#round to
> > return nonzero:"
> > p seed_values_triggering_misbehavior_with_four_zeroes
> > puts
> > puts "These numbers of zeroes between the decimal point and a 7 cause
> > BigDecimal#round to return nonzero:"
> > p number_of_zeroes_triggering_misbehavior
> >
> > ===== end code
> >
> > I get identical reports on Linux and Windows versions of Ruby:
> >
> > ruby 1.8.6 (2007-03-13 patchlevel 0) [i686-linux]
> >
> > ruby 1.8.6 (2007-03-13 patchlevel 0) [i386-mswin32]
> >
> > We would be grateful for a pointer to a patch that fixes this issue if
> > one is available.
>
> It seems to me as a bug. The code in trunk is the same, so I guess
> it's not fixed yet.
> Please file a bug at
> http://rubyforge.org/tracker/?func=add&group_id=426&atid=1698
> (rubyforge.org, project ruby)
>
> The problem is most probably in ext/bigdecimal/bigdecimal.c, VpMidRound().
>
> As you have probably noticed, it happens when 1. the number of leading
> zeros is divisible by 4 (BASE_FIG, the number of decimal digits stored
> in one U_LONG), and the next digit is >= 5 (I guess due to selected
> rounding mode)
>
> That means, the problematic numbers have format 0.XE-Y where X in
> [5..9] and Y%4 == 0
>
> It's even visible in
> BigDecimal.new("0.5").round(-4).to_i # => 10000
> BigDecimal.new("0.000000005").round(4) #=> 0.1E-3 == 0.0001
> BigDecimal.new("0.000000005").round(-4) #=> 0.1E5 == 10000
>
reported as #14271