Raymond Toy writes:
>> "Daniel" == Daniel Kochma writes:
>
> Daniel> Also, we'll have to define such infinity for each architecture
> Daniel> separately, depending on the endianess?
> >>
> >> Yes, probably. But you only need to set up MSB/LSB to get the right
> >> thing.
> "Daniel" == Daniel Kochma writes:
Daniel> Also, we'll have to define such infinity for each architecture
Daniel> separately, depending on the endianess?
>>
>> Yes, probably. But you only need to set up MSB/LSB to get the right
>> thing. I think. At least that's how fdl
Raymond Toy writes:
>> "Daniel" == Daniel Kochma writes:
>
> Daniel> Thanks for reply.
> Daniel> Raymond Toy writes:
>
> >>> "Daniel" == Daniel Kochma writes:
> >>
> Daniel> Hello,
> Daniel> I'm little in doubt. Problem is related to ieee-floating-point
> Da
> "Daniel" == Daniel Kochma writes:
Daniel> Thanks for reply.
Daniel> Raymond Toy writes:
>>> "Daniel" == Daniel Kochma writes:
>>
Daniel> Hello,
Daniel> I'm little in doubt. Problem is related to ieee-floating-point
Daniel> extensions, which provide infinit
Hi,
As I checked with the top-level repl, si::*break-level* is already 1.
If I eval (let ((si::*break-level* 1)) (si::tpl)) in the slime buffer,
it won't abort connection anymore. But I lose the capability of using
SLIME's debugging buffer. The errors will be directly dumped to the
top-level.
Anot
Thanks for reply.
Raymond Toy writes:
>> "Daniel" == Daniel Kochma writes:
>
> Daniel> Hello,
> Daniel> I'm little in doubt. Problem is related to ieee-floating-point
> Daniel> extensions, which provide infinities and nan. Everything works
> fine
> Daniel> until we generate
> "Daniel" == Daniel Kochma writes:
Daniel> Hello,
Daniel> I'm little in doubt. Problem is related to ieee-floating-point
Daniel> extensions, which provide infinities and nan. Everything works fine
Daniel> until we generate C code, which simply breaks, because it isn't
taken
Hello,
I'm little in doubt. Problem is related to ieee-floating-point
extensions, which provide infinities and nan. Everything works fine
until we generate C code, which simply breaks, because it isn't taken
into account.
There are two possible solutions:
- for these cases use constant expressio
