From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: uniform vector byte signed or unsigned
Date: Wed, 28 Jul 2004 08:42:33 +1000 [thread overview]
Message-ID: <87fz7d2ht2.fsf@zip.com.au> (raw)
In-Reply-To: <410239C7.8080701@ossau.uklinux.net> (Neil Jerram's message of "Sat, 24 Jul 2004 11:28:23 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
>
> My preference would be for the value to be unsigned in the first
> place, though.
Me too, but it's probably too late to change. I'd imagine everyone
who used it would have quickly found its signed, and written code for
that.
Actually, I see there's always a -128 to +127 check in array-fill!, so
I guess that answers the question what it ought to be.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-07-27 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 23:11 uniform vector byte signed or unsigned Kevin Ryde
2004-07-24 10:28 ` Neil Jerram
2004-07-27 22:42 ` Kevin Ryde [this message]
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=87fz7d2ht2.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).