[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Has bignumber support changed since 1.4?

From: Crowder, Brian
Subject: RE: Has bignumber support changed since 1.4?
Date: Mon, 10 Sep 2001 15:37:53 -0700

Unfortunately, I cannot run the guile interpreter under Windows with my
current port...  it bails reading the ice-9/boot-9.scm file with the
following error:

ERROR: In procedure struct-ref:
ERROR: Wrong type argument in position 2 (expecting INUMP): 5

Which is odd, since surely "5" ought to be an INUM (and the goo that makes
this variable is in C, and it's basically a SCM_MAKINUM() or whatever...

I had skipped over this issue, since my own code really doesn't require the
ice-9 stuff, but I guess I'll need to go back to it...

It will take me a little time to conjure a better example code...  but I'll
give it a go.

And if anyone has any thoughts on why my Windows build is so broken, please
feel free to comment.  :)  I'll gladly share that source and dsp/dsw if
anyone is interested.


-----Original Message-----
From: Dirk Herrmann [mailto:address@hidden
Sent: Monday, September 10, 2001 3:12 PM
To: Crowder, Brian
Cc: Guile Bug Mailing List
Subject: RE: Has bignumber support changed since 1.4?

On Mon, 10 Sep 2001, Crowder, Brian wrote:

> The (gc) in the homeworld.scm code will cause a crash on Win32, with a
> guile-1.5.1 I built...  (admittedly, the build is probably a bit sketchy,
> but I used the same technique on 1.4.1 and it worked okay --- configure
> under Cygwin tools, and then plug resulting files into MSVC project).

Sorry, but your code example is not very helpful.  Could you please try to
produce a _minimum_ but _complete_ piece of code that allows to reproduce
the error?  Since you are working with smobs, it is very likely that there
is something wrong with your smob code.

And, btw., bignums start at 536870912, at least on linux.  You can find
the corresponding constant by executing (+ most-positive-fixnum 1) at the 
guile prompt.

Best regards
Dirk Herrmann

reply via email to

[Prev in Thread] Current Thread [Next in Thread]