[#10853] Why limit class def to a constant or colon node? — Charles Oliver Nutter <charles.nutter@...>

Is there a historical reason why I can't do something like these:

12 messages 2007/04/03

[#10933] Cannot build with extra library path if previous version already installed — <noreply@...>

Bugs item #10140, was opened at 2007-04-16 17:32

10 messages 2007/04/16
[#10934] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — nobu@... 2007/04/16

Hi,

[#10960] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — "Michal Suchanek" <hramrach@...> 2007/04/18

On 4/16/07, nobu@ruby-lang.org <nobu@ruby-lang.org> wrote:

[#10967] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — Nobuyoshi Nakada <nobu@...> 2007/04/19

Hi,

[#10970] Re: [ ruby-Bugs-10140 ] Cannot build with extra library path if previous version already installed — "Michal Suchanek" <hramrach@...> 2007/04/19

On 4/19/07, Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:> Hi,>> At Wed, 18 Apr 2007 20:21:44 +0900,> Michal Suchanek wrote in [ruby-core:10960]:> > Yes. And this should also apply to extensions. The mkmf tests are now> > fine but the extension is linked with -L/sw/lib before -L../..>> Indeed.>>> Index: configure.in> ===================================================================> --- configure.in (revision 12191)> +++ configure.in (working copy)> @@ -1385,5 +1385,4 @@ if test "$enable_rpath" = yes; then> fi>> -LDFLAGS="-L. $LDFLAGS"> AC_SUBST(ARCHFILE)>This would break the previous fix so I did not even try to apply this ^

[#11003] miniruby loads extensions from already installed ruby — <noreply@...>

Bugs item #10303, was opened at 2007-04-23 10:44

10 messages 2007/04/23

[#11025] gsub with backslash characters in replacement string — "Adam Bozanich" <adam.boz@...>

Hello, spotted this one the other day:

10 messages 2007/04/26

Fwd: Bug in Bignum.to_s (1.8.6 only)

From: Ryan Davis <ryand-ruby@...>
Date: 2007-04-02 20:59:01 UTC
List: ruby-core #10839

Begin forwarded message:

> From: Daniel Azuma <dazuma@gmail.com>
> Date: March 31, 2007 10:27:44 AM PDT
> To: ruby-talk@ruby-lang.org (ruby-talk ML)
> Subject: Bug in Bignum.to_s (1.8.6 only)
> Reply-To: ruby-talk@ruby-lang.org
> X-Spam-Status: No, hits=0.4 required=5.0 tests=BAYES_01,ZSS_RUBY  
> autolearn=no  version=2.64-zss_spam_1_1_1
>
> Hello all,
>
> Just making a quick note of a bug we found in Bignum.to_s in Ruby  
> 1.8.6,
> in case it burns anyone else.
>
> Examples:
>
> irb(main):001:0> 18446744073709551615.to_s(36)  # should be
> "3w5e11264sgsf"
> => "w5e11264sgsf"
> irb(main):002:0> -18446744073709551615.to_s(8)  # should be
> "-1777777777777777777777"
> => "11777777777777777777777"
>
> The bug affects bases 8, 9, and 32-36 inclusive, over certain  
> ranges of
> values depending on the base. Values immediately less than 2**64  
> seem to
> be particularly affected. For example, in base 36, all values from
> 4738381338321616896 through 18446744073709551615 (which is 2**64-1)  
> will
> fail.
>
> It manifests only in Ruby 1.8.6. Ruby 1.8.5 works correctly. (It  
> appears
> that some optimization work went a little too far.)
>
> For anyone affected by this, I filed the bug on RubyForge, and  
> posted a
> possible "works for me, but use at your own risk" fix to bignum.c:
>
> http://rubyforge.org/tracker/? 
> func=detail&aid=9410&group_id=426&atid=1698
>
> Cheers,
> Daniel Azuma
> Chief Architect, Zoodango.com
>
> -- 
> Posted via http://www.ruby-forum.com/.
>


In This Thread

Prev Next