From: Kevin Ryde <noreply@savannah.gnu.org>
Subject: [bugs #11197] Error in string->number
Date: Sat, 04 Dec 2004 17:08:54 -0500 [thread overview]
Message-ID: <E1Cai5G-0005oj-96@lists.gnu.org> (raw)
This mail is an automated notification from the bugs tracker
of the project: Guile.
/**************************************************************************/
[bugs #11197] Latest Modifications:
Changes by:
Kevin Ryde <user42@zip.com.au>
'Date:
Sat 12/04/04 at 22:02 (Australia/NSW)
------------------ Additional Follow-up Comments ----------------------------
In fact only bases 2, 10 and 16 look right. Others have a bad bignum size calculation and overflow in various cases.
Only bases 2, 8, 10 and 16 are documented as supported, though others (below 16) are not explicitly rejected. Maybe that should change too.
/**************************************************************************/
[bugs #11197] Full Item Snapshot:
URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=11197>
Project: Guile
Submitted by: 0
On: Fri 12/03/04 at 08:10
Category: None
Severity: 5 - Average
Item Group: None
Resolution: None
Privacy: Public
Assigned to: None
Status: Open
Summary: Error in string->number
Original Submission: guile> (string->number "111111" 7)
19608
guile> (string->number "111111" 8)
37449
guile> (string->number "111111" 9)
<unnamed port>:4:1: In procedure bignum in expression (string->number "111111" 9):
<unnamed port>:4:1: Numerical overflow
ABORT: (numerical-overflow)
Type "(backtrace)" to get more information or "(debug)" to enter the debugger.
guile> (string->number "111111" 10)
111111
guile> (string->number "111111" 11)
177156
Follow-up Comments
------------------
-------------------------------------------------------
Date: Sat 12/04/04 at 22:02 By: Kevin Ryde <kryde>
In fact only bases 2, 10 and 16 look right. Others have a bad bignum size calculation and overflow in various cases.
Only bases 2, 8, 10 and 16 are documented as supported, though others (below 16) are not explicitly rejected. Maybe that should change too.
For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=11197>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2004-12-04 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 22:08 Kevin Ryde [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-28 23:47 [bugs #11197] Error in string->number Kevin Ryde
2004-12-08 23:25 Kevin Ryde
2004-12-03 8:16 anonymous
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=E1Cai5G-0005oj-96@lists.gnu.org \
--to=noreply@savannah.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).