[#22684] [Bug #1247] YAML::load converts some dates into strings — Matthew Wilson <redmine@...>

Bug #1247: YAML::load converts some dates into strings

10 messages 2009/03/05

[#22725] [Bug #1253] Fix MSVC Build Issues — Charlie Savage <redmine@...>

Bug #1253: Fix MSVC Build Issues

13 messages 2009/03/07

[#22727] Moving ruby 1.9.1 forward on windows — Charlie Savage <cfis@...>

Hi everyone,

14 messages 2009/03/08

[#22731] [Bug #1255] += for large strings egrigiously slow — James Lee <redmine@...>

Bug #1255: += for large strings egrigiously slow

11 messages 2009/03/08

[#22736] Ruby 1.9.1 and tail recursion optimization — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <ed.odanow@...>

Moin, moin!

13 messages 2009/03/08
[#22739] Re: Ruby 1.9.1 and tail recursion optimization — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <ed.odanow@...> 2009/03/08

Wolfgang N疆asi-Donner schrieb:

[#22748] [Feature #1256] Add constant TAILRECURSION to let a program recognize if tail recursion optimization is implemented — Wolfgang Nádasi-Donner <redmine@...>

Feature #1256: Add constant TAILRECURSION to let a program recognize if tail recursion optimization is implemented

7 messages 2009/03/08

[#22803] Relegate 1.8.6 to Engine Yard, part II — Urabe Shyouhei <shyouhei@...>

Hello and sorry for my being slow for this issue. It's OK now for me to pass

21 messages 2009/03/10

[#22812] [Bug #1261] cross-compiling Ruby extensions using mkmf doesn't fully respect DESTDIR — Daniel Golle <redmine@...>

Bug #1261: cross-compiling Ruby extensions using mkmf doesn't fully respect DESTDIR

8 messages 2009/03/10

[#22892] Ruby Time — valodzka <valodzka@...>

Got tired of current ruby Time limitation, I have written this -

24 messages 2009/03/14
[#22949] Re: Ruby Time — Tanaka Akira <akr@...> 2009/03/19

In article <9e19ed87-9d12-4f98-af3c-bd49a71b0bd4@p11g2000yqe.googlegroups.com>,

[#22974] Re: Ruby Time — valodzka <valodzka@...> 2009/03/20

[#22977] Re: Ruby Time — Urabe Shyouhei <shyouhei@...> 2009/03/20

valodzka wrote:

[#22981] Re: Ruby Time — valodzka <valodzka@...> 2009/03/21

> I bet you'll get tired of updating that database. There's a major difference

[#22893] [Feature #1291] O_CLOEXEC flag missing for Kernel::open — David Martin <redmine@...>

Feature #1291: O_CLOEXEC flag missing for Kernel::open

10 messages 2009/03/15

[#22939] [Bug #1303] A name considered a local variable on RHS of an assignment that defines it — Tomas Matousek <redmine@...>

Bug #1303: A name considered a local variable on RHS of an assignment that defines it

8 messages 2009/03/19

[#23063] [Bug #1332] Reading file on Windows is 500x slower then with previous Ruby version — Damjan Rems <redmine@...>

Bug #1332: Reading file on Windows is 500x slower then with previous Ruby version

11 messages 2009/03/30

[#23075] [Bug #1336] Change in string representation of Floats — Brian Ford <redmine@...>

Bug #1336: Change in string representation of Floats

37 messages 2009/03/31
[#23179] [Bug #1336] Change in string representation of Floats — Roger Pack <redmine@...> 2009/04/11

Issue #1336 has been updated by Roger Pack.

[#23181] Re: [Bug #1336] Change in string representation of Floats — Brent Roman <brent@...> 2009/04/11

[#23186] Re: [Bug #1336] Change in string representation of Floats — Yukihiro Matsumoto <matz@...> 2009/04/12

Hi,

[#23187] Re: [Bug #1336] Change in string representation of Floats — Brent Roman <brent@...> 2009/04/13

[#23188] Re: [Bug #1336] Change in string representation of Floats — Yukihiro Matsumoto <matz@...> 2009/04/13

Hi,

[ruby-core:22710] Re: suggestions for float

From: Jacob Fugal <lukfugl@...>
Date: 2009-03-07 04:16:17 UTC
List: ruby-core #22710
On Fri, Mar 6, 2009 at 6:20 PM, Daniel Luz <dev@mernen.com> wrote:
> Again, what about something like Python's?
>
> =A0>>> str(0.1) =A0 =A0 =A0 =A0 =A0# equivalent to Ruby's #to_s
> =A0'0.1'
> =A0>>> repr(0.1) =A0 =A0 =A0 =A0 # equivalent to Ruby's #inspect
> =A0'0.10000000000000001'
> =A0>>> print 0.1 =A0 =A0 =A0 =A0 # print casts to string, just like Ruby'=
s puts
> =A00.1
> =A0>>> 0.1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 # the interactive interpreter uses=
 repr, like irb
> =A00.10000000000000001
> =A0>>> 2.1 - 3.0
> =A0-0.89999999999999991
>
> Keeping #to_s behavior unchanged would break very little existing
> code, and having #inspect return something that allows reconstructing
> the same object is generally a very nice thing, IMO.

I feel a lot more comfortable "fixing" Float#inspect to be more
verbose than I do Float#to_s. I'm against changing Float#to_s in the
ways proposed, but can accept changing Float#inspect.

That said, I do a lot of number crunching in irb; if I want some quick
calculator action, for instance, I just fire up irb and go at it. I,
personally, don't want to see a bunch of extra digits that I am
already aware of in the back of my mind but which aren't relevant for
me.

To accomodate both worlds, let's be sure to include a means to revert
to the old Float#inspect (without redefining it ourselves) that could
be included in .irbrc files. The default can be the verbose
Float#inspect, but easily overridden for users who like the old
behavior.

Jacob Fugal

In This Thread