From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: [9fans] PCC - #if
Date: Fri, 4 May 2007 22:23:29 +0200 [thread overview]
Message-ID: <c4167ab1c8e9bbe37e8b8fe0af747a37@proxima.alt.za> (raw)
I have the following diff:
term% diff ../../../openldap-2.3.32/include/ac/time.h ../../include/ac
20c20
< #if defined(TIME_WITH_SYS_TIME)
---
> #if TIME_WITH_SYS_TIME
23c23
< #elif defined(HAVE_SYS_TIME_H)
---
> #elif HAVE_SYS_TIME_H
and I'm curious whether it's a slip in the OpenLDAP source or in PCC
that the one works and the other doesn't. I do not have an ANSI
standard to check against, but my gut feel is that OpenLDAP is
stretching a limit. If not, then PCC ought to be corrected, it
reports (the "elsif" is certainly mistaken):
cpp: ../../include/ac/time.h:20 csn.c:47 Syntax error in #if/#elsif
++L
next reply other threads:[~2007-05-04 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 20:23 lucio [this message]
2007-05-04 21:17 ` Russ Cox
2007-05-04 21:35 ` lucio
2007-05-04 21:56 ` geoff
2007-05-04 21:57 ` Russ Cox
2007-05-04 20:32 lucio
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4167ab1c8e9bbe37e8b8fe0af747a37@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).