[#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: "Florian Frank" <flori@...>
Date: 2005-08-03 23:32:41 UTC
List: ruby-core #5527
Austin Ziegler wrote:

>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.
>
It does.

>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 ...
>  
>
I dependend on 1 / 0.0 giving Infinity, but it now raises a 
FloatDomainError. That's how I stumbled over the above change. Work 
around could be 1.0 / 0.0. Or is this a bug, too?

-- 
Florian Frank


In This Thread