exact and inexact numbers should not be eqv?

[GoogleCodeExporter]

What steps will reproduce the problem?
mosh> (define x 4)
mosh> (define y 4.0)
mosh> (exact? x)
#t
mosh> (inexact? x)
#f
mosh> (exact? y)
#f
mosh> (inexact? y)
#t
mosh> (eqv? x y)
#t

What is the expected output? What do you see instead?
Expected (eqv? x y) => #f
Instead (eqv? x y) => #t

What version of the product are you using? On what operating system?
Linux glimworm 2.6.39-2-amd64 #1 SMP Wed Jun 8 11:01:04 UTC 2011 x86_64 
GNU/Linux
Mosh R6RS scheme interpreter, version 0.2.7 (mosh-0.2.7-337-ged93abc Mon, 27 
Jun 2011 13:41:16 +0900) 

Please provide any additional information below.
R6RS: "The eqv? procedure returns #f if one of the following holds:... One of 
obj1 and obj2 is an exact number object but the other is an inexact number 
object."

Original issue reported on code.google.com by amoe...@gmail.com on 29 Jun 2011 at 11:50

[GoogleCodeExporter]

Original comment by hige...@gmail.com on 29 Jun 2011 at 12:40

• Changed state: Accepted

[GoogleCodeExporter]

Fixed.
https://github.com/higepon/mosh/commit/c112f2794d85cd8244805a8c9939ef24704dc085

This fix reveals an another bug on string->number.
make testR fails. Not fixed yet.

Original comment by hige...@gmail.com on 1 Jul 2011 at 8:13

• Changed state: Fixed