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: Portability bug with UINTPTR_MAX in Solaris/Forte
Date: Tue, 24 Jun 2003 09:05:34 +1000	[thread overview]
Message-ID: <87wufcqts1.fsf@zip.com.au> (raw)
In-Reply-To: <uw5of0prw7k.fsf@saturn.math.uni-magdeburg.de> (Matthias Koeppe's message of "Mon, 23 Jun 2003 11:15:27 +0200")

Matthias Koeppe <mkoeppe@merkur.math.uni-magdeburg.de> writes:
>
> (I still think that tricky
> things like this should be checked at `configure' time, rather than
> during compilation, though.)

Oh, well, no need to add to the configure script if a cpp conditional
can do it cleanly and portably.

> +/* On Solaris 7 and 8, /usr/include/sys/int_limits.h defines
> +   INTPTR_MAX and UINTPTR_MAX to empty, INTPTR_MIN is not defined.

That's a typo there is it?  Only UINTPTR_MAX defined to empty.

> +#if SCM_SIZEOF_INTPTR_T != 0 && defined(INTPTR_MAX) && defined(INTPTR_MIN) && INTPTR_MAX-0 != 0 && INTPTR_MIN-0 != 0

While you're at it you might like to merge the tests so scm_t_bits and
scm_t_signed_bits are both based on "intptr" stuff, or both on "long",
rather than having separate conditionals.  Wouldn't want them to come
out different.


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


  reply	other threads:[~2003-06-23 23:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18  6:25 Portability bug with UINTPTR_MAX in Solaris/Forte Matthias Koeppe
2003-06-21  1:20 ` Kevin Ryde
2003-06-23  9:15   ` Matthias Koeppe
2003-06-23 23:05     ` Kevin Ryde [this message]
2003-06-25 15:17       ` Matthias Koeppe
2003-07-05  0:03         ` 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=87wufcqts1.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).