unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Uniform vector lengths -- how long?
Date: Sat, 10 Jul 2004 10:41:25 +1000	[thread overview]
Message-ID: <87zn68ithm.fsf@zip.com.au> (raw)
In-Reply-To: <87wu21cvyz.fsf@trouble.defaultvalue.org> (Rob Browning's message of "Mon, 21 Jun 2004 00:37:40 -0500")

Rob Browning <rlb@defaultvalue.org> writes:
>
> I suppose we should use scm_num2ulong in make-FOOvector and friends,
> rather then SCM_INUM.

I suppose, though personally I wouldn't feel any great urgency for
that.  A positive inum ends up only, what, 3 bits less than a ulong,
and a 512Mb array would be more than likely bigger than one could do
real work with on a 32-bit machine.

What is worth worrying about though would be making sure the "len *
uvec_sizes[type]" in make_uvec doesn't overflow, perhaps wrapping
around to a small size which is successfully malloced.  I guess
currently with a maximum 8 in uvec_sizes and maximum
MOST_POSITIVE_INUM for the count it's ok.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2004-07-10  0:41 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 [this message]
2004-07-12 15:04       ` Rob Browning
2004-07-22  1:20         ` Kevin Ryde
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=87zn68ithm.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).