From: "Scott N. Walck" <walck@lvc.edu>
To: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: set-current-module in .guile ?
Date: Tue, 8 Apr 2008 11:41:39 -0400 [thread overview]
Message-ID: <18427.37427.432863.278831@entangle.lvc.edu> (raw)
In-Reply-To: <87ej9g4g8g.fsf@gnu.org>
Hi,
I'm using SLIB 3a5 and Guile 1.8.3. I've had trouble with SLIB 3b1
also.
Scott
Ludovic Courtès writes:
> Hi,
>
> "Scott N. Walck" <walck@lvc.edu> writes:
>
> > [walck@entangle:~]$ guile
> > guile> (load "/usr/local/src/guile-scmutils/src/load.scm")
> > guile> (module-use! (current-module) generic-environment)
> > #f
> > guile> +
> > #<procedure g:+ args>
> > guile> (+ (vector 5 6) (vector 7 8))
> > Segmentation fault (core dumped)
>
> It starts looking like something worrying from the Guile side. ;-)
>
> I tried installing guile-scmutils to reproduce the problem but failed.
> What version of Guile and SLIB are you using?
>
> With SLIB 3b1 and Guile HEAD, I get:
>
> $ guile -L ~/soft/lib/ -l load.scm
> Backtrace:
> In unknown file:
> ?: 0* [primitive-load "/home/ludo/soft/lib/slib/factor.scm"]
> In /home/ludo/soft/lib/slib/factor.scm:
> 90: 1* (define prime:sieve (bytes 0 0 1 1 0 1 0 1 ...))
> 90: 2 (define-public prime:sieve (bytes 0 0 1 1 0 1 0 1 ...))
> 90: 3 (begin (define-private prime:sieve (bytes 0 0 1 ...)) (eval-case (# #)))
> In unknown file:
> ?: 4* (define-private prime:sieve (bytes 0 0 1 1 0 1 0 1 ...))
> In /home/ludo/soft/lib/slib/factor.scm:
> 90: 5* [bytes 0 0 1 1 0 1 0 1 ...]
> In /home/ludo/soft/lib/slib/byte.scm:
> 61: 6 [list->array 1 #u32(32) (0 0 1 1 0 1 0 1 0 ...)]
>
> /home/ludo/soft/lib/slib/byte.scm:61:3: In procedure list->array in expression (list->array 1 (A:fixN8b) ...):
> /home/ludo/soft/lib/slib/byte.scm:61:3: Wrong number of arguments to #<primitive-procedure list->array>
>
> (Where `~/soft/lib' is that path to SLIB and `load.scm' is
> guile-scmutils' load file.)
>
> Actually, SLIB's `array' module isn't accessible from Guile for some
> reason:
>
> guile> (use-modules (ice-9 slib))
> guile> (require 'array)
> #t
> guile> array?
> #<primitive-procedure array?> ;; <--- This is Guile's built-in proc
> guile> A:bool
> #<procedure at1 opt> ;; <--- but this one's from SLIB
>
> Any idea?
>
> Thanks,
> Ludovic.
>
>
>
>
--
Scott N. Walck
Associate Professor of Physics
Lebanon Valley College
Annville, PA 17003
phone: 717-867-6153
fax: 717-867-6075
email: walck@lvc.edu
next prev parent reply other threads:[~2008-04-08 15:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 17:24 set-current-module in .guile ? Scott N. Walck
2008-04-05 21:00 ` Jon Wilson
2008-04-06 0:01 ` Walck, Scott
2008-04-06 14:58 ` Ludovic Courtès
2008-04-07 1:27 ` Walck, Scott
2008-04-07 7:16 ` Ludovic Courtès
2008-04-07 11:27 ` Walck, Scott
2008-04-07 13:38 ` Ludovic Courtès
2008-04-07 15:07 ` Scott N. Walck
2008-04-08 13:40 ` Ludovic Courtès
2008-04-08 15:41 ` Scott N. Walck [this message]
2008-04-09 15:05 ` Ludovic Courtès
2008-04-09 15:24 ` Walck, Scott
2008-04-09 20:16 ` Neil Jerram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18427.37427.432863.278831@entangle.lvc.edu \
--to=walck@lvc.edu \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).