From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: further hacking on guile-vm
Date: Thu, 15 May 2008 03:52:30 +0200 [thread overview]
Message-ID: <87od78nxk1.fsf@gnu.org> (raw)
In-Reply-To: m3r6c7jiqc.fsf@pobox.com
Hello!
Andy Wingo <wingo@pobox.com> writes:
> So, I have been poking more at guile-vm. The focus of this patchset is
> on repl usability.
Looks cool!
I pulled from your branch and stumbled upon commit
7d1c45d38e34659c1ec3b76ba4c985901123bf61 entitled "fix macro compilation
via hooking into eval-case", which will probably lead to discussions.
;-)
I wanted to try a few things to refresh my memory on that topic, but it
appears that `pprint-glil' is currently broken:
guile> (use-modules (system il compile) (language scheme translate))
guile> (define hi (translate '(use-modules (srfi srfi-9)) (make-module)))
guile> (define lo (compile hi (make-module)))
guile> (use-modules (system il glil))
guile> (pprint-glil lo)
Backtrace:
In current input:
6: 0* [pprint-glil #<<glil-asm> vars: # body: #>]
In ../module/system/il/glil.scm:
195: 1 (let* ((port (if # # ...))) ((letrec (#) print) (unparse glil) 0) ...)
196: 2* [print ...
196: 3* [unparse #<<glil-asm> vars: # body: #>]
163: 4 (record-case glil ((<glil-asm> vars body) (quasiquote (@asm # #))) ...)
...
166: 5 (quasiquote (@asm (# # # #) (unquote-splicing #)))
168: 6* [map #<procedure unparse (glil)> (# # # # ...)]
In unknown file:
?: 7* [unparse #<<glil-source> loc: {#f}>]
In ../module/system/il/glil.scm:
163: 8* (let* ((#{\ g28}# glil)) (cond (# #) (# #) (# #) ...))
In unknown file:
?: 9 (cond ((# #{\ g28}#) (let # #)) ((# #{\ g28}#) (let # #)) ...)
In ../module/system/il/glil.scm:
...
171: 10 (quasiquote (@source (unquote (car loc)) (unquote (cdr loc))))
171: 11* [cdr {#f}]
../module/system/il/glil.scm:171:48: In procedure cdr in expression (cdr loc):
../module/system/il/glil.scm:171:48: Wrong type (expecting pair): #f
ABORT: (wrong-type-arg)
Any idea?
Surely you can achieve similar results more quickly using the REPL?
Thanks,
Ludovic.
prev parent reply other threads:[~2008-05-15 1:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 21:49 further hacking on guile-vm Andy Wingo
2008-05-15 1:52 ` Ludovic Courtès [this message]
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=87od78nxk1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).