From: Kjetil Matheussen <INVALID.NOREPLY@gnu.org>
To: Kjetil Matheussen <k.s.matheussen@notam02.no>, bug-guile@gnu.org
Subject: [bug #27168] Strange reader bug (string->number)
Date: Tue, 04 Aug 2009 07:45:09 +0000 [thread overview]
Message-ID: <20090804-074507.sv74755.75776@savannah.gnu.org> (raw)
In-Reply-To:
URL:
<http://savannah.gnu.org/bugs/?27168>
Summary: Strange reader bug (string->number)
Project: Guile
Submitted by: kjetil_m
Submitted on: Tue 04 Aug 2009 07:45:07 AM GMT
Category: None
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
_______________________________________________________
Details:
The following bug causes some problems
with Snd: (At least the realtime extension of Snd)
*****************************
$ echo "'(4194304 262144 1.0f)" >test.scm
$ guile -l test.scm
Backtrace:
In unknown file:
?: 0* [primitive-load "test.scm"]
<unnamed port>: In procedure string->number in expression (primitive-load
name):
<unnamed port>: Value out of range: 444
$ *****************************
* Tested with Guile 1.8.6 and 1.8.0. Same behaviour for both.
* It only happens when using "guile -f <filename>" from the
command line or evaluating (load <filename>) in the REPL.
* Evaluating '(4194304 262144 1.0f) in the REPL causes no error.
* Examples of lists not causing an error:
'(4194304 262144 1.0)
'(262144 1.0f)
'(4194304 1.0f)
'(1 2 3.0f)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?27168>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next reply other threads:[~2009-08-04 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-04 7:45 Kjetil Matheussen [this message]
2009-08-04 18:39 ` [bug #27168] Strange reader bug (string->number) Andy Wingo
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=20090804-074507.sv74755.75776@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=k.s.matheussen@notam02.no \
/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).