From: Kevin Ryde <user42@zip.com.au>
Subject: scm_t_bits versus uintptr_t
Date: Sat, 24 May 2003 09:03:39 +1000 [thread overview]
Message-ID: <878ysxl0z8.fsf@zip.com.au> (raw)
While looking at some preprocessor output I noticed scm_t_bits is
coming out as plain unsigned long on my i386 debian with gcc 3.3.
It seems INTPTR_MAX and INTPTR_MIN are defined in stdint.h in glibc
(2.3.1) and not in limits.h, so tags.h decides intptr_t can't be used.
It might be necessary to include inttypes.h or stdint.h, or whichever
is available, if the intention is to use intptr_t when possible.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2003-05-23 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 23:03 Kevin Ryde [this message]
2003-06-01 21:22 ` scm_t_bits versus uintptr_t Marius Vollmer
2003-06-06 22:29 ` 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=878ysxl0z8.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).