From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: limits for (export ...)
Date: Sat, 29 Oct 2011 22:35:56 +0200 [thread overview]
Message-ID: <87boszsfgz.fsf@gnu.org> (raw)
In-Reply-To: m31utvd6um.fsf@googlemail.com
Hi,
Ian Price <ianprice90@googlemail.com> skribis:
> Although, and I don't think this is related to your issue, when
> trying out the (list sym0 ...) from the repl, I did get an error
>
> scheme@(guile−user)> (list sym0 sym1 ... sym100 sym101)
> ;;; <stdin>:3:0: warning: possibly unbound variable `sy'
> ;;; <stdin>:3:0: warning: possibly unbound variable `m85'
> <unnamed port>:3:0: In procedure #<procedure a08bf50 at <current input>:3:0 ()>:
> <unnamed port>:3:0: In procedure module−lookup: Unbound variable: sy
>
> Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
> scheme@(guile−user) [1]> ,q
>
> But further exploration shows that all the symbols are in fact bound,
> and this error only seems to occur if there is no line break at some
> point after sym8 and before sym85. Presumably, I'm running up against
> some reader limit there.
Weird. I can’t reproduce it this way:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (use-modules(srfi srfi-1))
scheme@(guile-user)> (define syms (unfold (lambda (i) (> i 1234)) (lambda (i) (string->symbol (format #f "sym~a" i))) 1+ 0))
scheme@(guile-user)> (define s (with-output-to-string (lambda () (write syms))))
scheme@(guile-user)> (equal? syms (call-with-input-string s read))
$6 = #t
--8<---------------cut here---------------end--------------->8---
Could you see if you can find a way to reproduce the problem?
Thanks,
Ludo’.
next prev parent reply other threads:[~2011-10-29 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 16:40 limits for (export ...) Pavel V. Kaygorodov
2011-10-29 17:51 ` Ian Price
2011-10-29 20:35 ` Ludovic Courtès [this message]
2011-10-29 22:50 ` Ian Price
2011-10-29 23:09 ` Ian Price
2011-10-31 21:07 ` Thien-Thi Nguyen
2011-10-29 20:36 ` Ludovic Courtès
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=87boszsfgz.fsf@gnu.org \
--to=ludo@gnu.org \
--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).