From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Uniform vector lengths -- how long?
Date: Thu, 22 Jul 2004 11:20:32 +1000 [thread overview]
Message-ID: <87iscgu9b3.fsf@zip.com.au> (raw)
In-Reply-To: 87isctl122.fsf@trouble.defaultvalue.org
Rob Browning <rlb@defaultvalue.org> writes:
>
> SIZE_MAX being defined
I think, but don't quote me, that limits.h and SIZE_MAX are ANSI C,
and guile already demands that.
> if (len > ((size_t) SIZE_MAX / uvec_sizes[type])) ...
Since uvec_sizes are all powers of 2, perhaps change to a
uvec_shift[type] array and use a shift instead of a division. Ditto
shift instead of multiply for the len -> bytes.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-07-22 1:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 21:00 Uniform vector lengths -- how long? Rob Browning
2004-06-20 23:26 ` Kevin Ryde
2004-06-21 5:37 ` Rob Browning
2004-07-10 0:41 ` Kevin Ryde
2004-07-12 15:04 ` Rob Browning
2004-07-22 1:20 ` Kevin Ryde [this message]
2004-08-04 14:37 ` 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=87iscgu9b3.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).