Re: how to compute
"Pierpaolo BERNARDI" <[email protected]> Wed, 17 May 2006 05:40:14 +0200
| Newsgroups | gmane.lisp.allegro |
|---|---|
| Message-ID | <op.s9oe5cwr8t8izc@eraora> |
On Wed, 17 May 2006 03:51:57 +0200, Steve Haflich <[email protected]> wrote: > From: "Pierpaolo BERNARDI" <[email protected]> > BTW, I think the following is a small bug in acl: > CL-USER(153): 6042715942219502152353483497843569525253244555916134.0 > Error: This integer is too large to be converted to single float: > 343488630960564478300511837005615234375 > [condition type: SIMPLE-ERROR] > (there's no integer in my code, and the value printed is bogus) >I'm curious why you think this is a bug, whether small or otherwise. > What did you expect to be the result of executing this form? What do > you find wrong about the result? That execution signaled error? Or > that the error wasn't what you expected? The error wasn't what I expected. I expected an error message like: CL-USER(153): 6042715942219502152353483497843569525253244555916134.0 Error: This number is too large to be represented as single float: 6042715942219502152353483497843569525253244555916134.0 [condition type: SIMPLE-ERROR] but your explanation is convincing, and I retract my statement. > First, why do you think the integer value in the error message is > bogus? It look likes the printed representation of a perfectly > reasonable integer. (If that integer were truly bogus, then we would > be in danger of the sun stopping to shine and cracks appearing in the > sky. :-) Rather, you should have said that you don't understand where > that integer comes from. Well, things I don't understand are bogus, of course. 8^) (Just kidding). Thanks. P.