From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: make-regexp error memory leak
Date: Sat, 24 Jul 2004 09:06:37 +1000 [thread overview]
Message-ID: <878ydajpc2.fsf@zip.com.au> (raw)
In-Reply-To: 87ekniqtjl.fsf@trouble.defaultvalue.org
Rob Browning <rlb@defaultvalue.org> writes:
>
> For example, try storing a large number in a
> 64-bit vector -- the printed representations are wrong.
Ah, a bit dodgy that.
If you're hunting dodginess, it looks like make-s16vector may assume a
short is 16-bits when converting the "fill" parameter from an SCM. A
system with a bigger short probably gets values silently truncated
instead of provoking range errors. Similarly u16, and s32 and u32
with "int".
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-07-23 23:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 23:51 make-regexp error memory leak Kevin Ryde
2004-07-07 17:41 ` Rob Browning
2004-07-08 23:57 ` Kevin Ryde
2004-07-09 18:03 ` Rob Browning
2004-07-10 0:05 ` Kevin Ryde
2004-07-11 18:37 ` Rob Browning
2004-07-23 23:06 ` Kevin Ryde [this message]
2004-07-27 1:56 ` Rob Browning
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=878ydajpc2.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).