From: Kevin Ryde <user42@zip.com.au>
Subject: uniform vector byte signed or unsigned
Date: Sat, 24 Jul 2004 09:11:40 +1000 [thread overview]
Message-ID: <87zn5qiaj7.fsf@zip.com.au> (raw)
In scm_cvref it looks like a byvect byte is fetched as a "char", which
is of course normally signed, but on some systems can be unsigned.
Is a byte meant to be treated as signed? It's probably worth making
that explicit so scheme level stuff doesn't depend on the vagaries of
C type conventions.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-07-23 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 23:11 Kevin Ryde [this message]
2004-07-24 10:28 ` uniform vector byte signed or unsigned Neil Jerram
2004-07-27 22:42 ` Kevin Ryde
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=87zn5qiaj7.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).