[#5563] Non-overridable and non-redefinable methods — Eric Mahurin <eric_mahurin@...>

Lately, I've been thinking about the future of ruby

44 messages 2005/08/19
[#5564] Re: Non-overridable and non-redefinable methods — Austin Ziegler <halostatue@...> 2005/08/19

On 8/19/05, Eric Mahurin <eric_mahurin@yahoo.com> wrote:

[#5571] Re: Non-overridable and non-redefinable methods — Eric Mahurin <eric_mahurin@...> 2005/08/19

--- Austin Ziegler <halostatue@gmail.com> wrote:

[#5574] Re: Non-overridable and non-redefinable methods — TRANS <transfire@...> 2005/08/20

Just wanted to add a few things.

[#5581] Re: Non-overridable and non-redefinable methods — Austin Ziegler <halostatue@...> 2005/08/20

On 8/19/05, TRANS <transfire@gmail.com> wrote:

[#5583] Re: Non-overridable and non-redefinable methods — "David A. Black" <dblack@...> 2005/08/20

Hi --

[#5585] Re: Non-overridable and non-redefinable methods — Eric Mahurin <eric_mahurin@...> 2005/08/20

--- "David A. Black" <dblack@wobblini.net> wrote:

[#5609] Pathname#walk for traversing path nodes (patch) — ES <ruby-ml@...>

Here is a small addition to Pathname against 1.9, probably suited

20 messages 2005/08/22

Re: Division weirdness in 1.9

From: Austin Ziegler <halostatue@...>
Date: 2005-08-03 23:18:46 UTC
List: ruby-core #5525
On 8/3/05, Florian Frank <flori@nixe.ping.de> wrote:
> Hi,
> 
> p [ 1 / 3.0, 1.0 / 3 ] # => [0, 0.333333333333333]
> 
> I expected the first to be equal to the second. This was
> 
> ruby 1.9.0 (2005-08-04) [i686-linux]
> 
> Is this a bug? If not, do you people really think this is a good idea?

Smells like a bug, to me. If this:

  a = 1
  b = 3
  p [ a / b.to_f, a.to_f / b ]

does the same, it's definitely a bug. This is a behaviour that
PDF::Writer depends on (casting one parameter to a float makes the
expression a float expression). I can work around it, but ...

-austin
-- 
Austin Ziegler * halostatue@gmail.com
               * Alternate: austin@halostatue.ca


In This Thread