From: Tony Arcieri <tony.arcieri@...>
Date: 2010-12-24T09:34:50+09:00
Subject: Re: Best way to get 3/2 == 1.5 ?

--0016e6d6456f4dbea204981d27cc
Content-Type: text/plain; charset=ISO-8859-1

For what it's worth, I read something Matz said once along the lines that
3/2 should probably be 1.5.

That said, you can monkeypatch integer division to have different
semantics. I would definitely NOT recommend doing this, but it does show you
the power of Ruby:

class Fixnum
  alias :divide :/

  def /(n)
    if self % n == 0
      self.divide(n)
    else
      self.to_f / n
    end
  end
end


On Thu, Dec 23, 2010 at 3:19 PM, Stefan Salewski <mail@ssalewski.de> wrote:

> I really like to get "real/float" division results. I know that there
> are cases where one may need integer results, but for most of my
> applications I do not want it. For example for may cairo drawing test at
> http://www.ssalewski.de/PetEd-Demo.html.en unwanted integer results was
> a reason for some strange bugs.
>
> For Python there was something like "from future import division" to fix
> it. In Ruby we can use 3.to_f / 2 or 3.fdiv 2. I am not really happy
> with that notation, because I should use that always to ensure that I
> get always my desired result.
>
> Is there a simple way to redefine division, like Pythons  "from future
> import division"?. I have found a few tricks with Google (which I, still
> learning Ruby, do not really understand), but I am no expert, so I do
> not want to break something with ugly redefinition tricks.
>
> Best regards
>
> Stefan Salewski
>
>
>
>


-- 
Tony Arcieri
Medioh! Kudelski

--0016e6d6456f4dbea204981d27cc--