[#23657] [Bug #1550] String#lstrip! raises RuntimeError on Frozen String Despite Making No Changes — Run Paint Run Run <redmine@...>

Bug #1550: String#lstrip! raises RuntimeError on Frozen String Despite Making No Changes

13 messages 2009/06/01

[#23729] [Bug #1583] Time + String no Longer Raises TypeError? — Run Paint Run Run <redmine@...>

Bug #1583: Time + String no Longer Raises TypeError?

14 messages 2009/06/05

[#23770] [Bug #1595] rake unusable on windows install — Robert Gonzalez <redmine@...>

Bug #1595: rake unusable on windows install

10 messages 2009/06/09

[#23869] [Bug #1640] [PATCH] Documentation for the Rational Class — Run Paint Run Run <redmine@...>

Bug #1640: [PATCH] Documentation for the Rational Class

12 messages 2009/06/16

[#23903] [Bug #1648] Rational#div Raises NoMethodError for Invalid Argument — Run Paint Run Run <redmine@...>

Bug #1648: Rational#div Raises NoMethodError for Invalid Argument

9 messages 2009/06/17

[#23977] [ANN] meeting log of RubyDeveloperKaigi20090622 — "Yugui (Yuki Sonoda)" <yugui@...>

Hi,

41 messages 2009/06/23
[#23979] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — Run Paint Run Run <runrun@...> 2009/06/23

Thanks for the update. :-)

[#24173] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — "NARUSE, Yui" <naruse@...> 2009/07/07

Sorry for late response,

[#24174] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — Luis Lavena <luislavena@...> 2009/07/07

On Tue, Jul 7, 2009 at 12:12 AM, NARUSE, Yui<naruse@airemix.jp> wrote:

[#24242] Re: [ANN] meeting log of RubyDeveloperKaigi20090622 — Charles Oliver Nutter <headius@...> 2009/07/09

On Mon, Jul 6, 2009 at 10:18 PM, Luis Lavena<luislavena@gmail.com> wrote:

[#24010] [Bug #1685] Some windows unicode path issues remain — B Kelly <redmine@...>

Bug #1685: Some windows unicode path issues remain

26 messages 2009/06/24
[#29189] [Bug #1685] Some windows unicode path issues remain — Yuki Sonoda <redmine@...> 2010/04/01

Issue #1685 has been updated by Yuki Sonoda.

[#29200] Re: [Bug #1685] Some windows unicode path issues remain — Bill Kelly <billk@...> 2010/04/01

Yuki Sonoda wrote:

[#29892] Re: [Bug #1685] Some windows unicode path issues remain — Bill Kelly <billk@...> 2010/04/29

Hi,

[#24058] [Bug #1696] http downloads are unuseably slow — Steven Hartland <redmine@...>

Bug #1696: http downloads are unuseably slow

19 messages 2009/06/27

[#24063] [Feature #1697] Object#<=> — Marc-Andre Lafortune <redmine@...>

Feature #1697: Object#<=>

15 messages 2009/06/28

[ruby-core:23856] Re: Differences in Rational Between 1.8 and 1.9

From: Yukihiro Matsumoto <matz@...>
Date: 2009-06-14 23:53:29 UTC
List: ruby-core #23856
Hi,

In message "Re: [ruby-core:23843] Differences in Rational Between 1.8 and 1.9"
    on Sun, 14 Jun 2009 06:34:43 +0900, Run Paint Run Run <runrun@runpaint.org> writes:

|1) 1.8 used the Rational::Unify constant to determine whether
|Rational(integer) should return a Fixnum or a Rational. 1.9 doesn't
|support this functionality.
|2) 1.8 had a #new! constructor that created a Rational without
|reducing its arguments; 1.9 doesn't appear to have an alternative.
|3) Rational#coerce tried to call #to_f on its argument on 1.8; it
|doesn't on 1.9.
|4) 1.8 had a Rational.allocate method that returned Rational(nil,
|nil). Given that this invocation is illegal under 1.9, and rational.c
|contains "rb_undef_method(CLASS_OF(rb_cRational), "allocate");", I
|assume it has been removed intentionally.
|5) Rational.reduce has been removed, presumably because Rational now
|automatically reduces. However, if #new!, or something similar, is
|reimplemented, would this be restored?
|6) Rational#to_s returns "n/d" and Rational#inspect returns "(n/d)".
|7) On 1.8 #inspect returned a string that could be eval'd to give
|self; it doesn't on 1.9.

All of above are intentional.  No need to file bug.  Most of them are
removing internal that need to be there to implement rational in Ruby.
6) and 7) are preparation for Rational literals, which is planned for
the future.

|8) There is no documentation. Would a patch be accepted, or is
|somebody working on this?

The patch will be accepted.  No one is working on, as far as I know.

|9) These changes, assuming intentionality, are not documented in
|doc/NEWS-1.9.1. Would a ticket to rectify this be appropriate?

Since they are considered by internal changes, it did not appear in
NEWS file.

							matz.

In This Thread