From: Mike Gran <spk121@yahoo.com>
Cc: bug-guile@gnu.org, "John W. Eaton" <jwe@bevo.che.wisc.edu>
Subject: Re: 1.8.0: C++-style cast
Date: Wed, 12 Jul 2006 19:13:23 -0700 (PDT) [thread overview]
Message-ID: <20060713021323.78321.qmail@web37914.mail.mud.yahoo.com> (raw)
In-Reply-To: <874pxmmg0e.fsf@zip.com.au>
--- Kevin Ryde <user42@zip.com.au> wrote:
> I don't think it's c++. I'm guessing X_CAST is an OSF macro. Dunno
> if it does anything good. John Eaton contributed that, maybe he can
> say (Cc'ed).
>
You're right. When I googled for X_CAST, I came across this...
http://www.belgeler.org/autobook/autobook-Changeable-C--.html
which I didn't read too closely and took to understand that X_CAST was
C++ (which I don't use much.) It also showed up in the Octave source,
which is C++, to reinforce my misperception.
For what it is worth, one of the strange machines I've been trying to
compile on (powerpc-ibm-aix4.3.3.0) has the code below in float.h and
math.h, which seems to align with the intent of the X_CAST in the guile
source.
extern unsigned int _DBLINF[2];
#define DINFINITY _DBLINF
#define DBL_INFINITY (*((double *) (_DBLINF)))
#define DBL_QNAN (*((double *) (DQNAN)))
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
prev parent reply other threads:[~2006-07-13 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 3:58 1.8.0: C++-style cast Mike Gran
2006-07-12 8:20 ` Ludovic Courtès
2006-07-21 0:34 ` Kevin Ryde
2006-07-13 1:48 ` Kevin Ryde
2006-07-13 1:59 ` John W. Eaton
2006-07-13 2:13 ` Mike Gran [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=20060713021323.78321.qmail@web37914.mail.mud.yahoo.com \
--to=spk121@yahoo.com \
--cc=bug-guile@gnu.org \
--cc=jwe@bevo.che.wisc.edu \
--cc=spikegran@earthlink.net \
/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).