From: Zefram <A.Main@dcs.warwick.ac.uk>
To: hzoli@cs.elte.hu (Zoltan Hidvegi)
Cc: hniksic@public.srce.hr, zsh-workers@math.gatech.edu
Subject: Re: Compilation on Ultrix cc
Date: Wed, 8 May 1996 15:54:29 +0100 (BST) [thread overview]
Message-ID: <3061.199605081454@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <199605072039.WAA24281@turan.elte.hu> from "Zoltan Hidvegi" at May 7, 96 10:39:51 pm
>The patch below should remove the warnings on Ultix with cc. It removes
>the #ifdef ULTRIX lines from glob.c and always uses Statptr in place of
>struct stat *. I also removed the #error directive from builtin.c and
>repladed with comething which should generate a syntax error (but I hope
>that noone will see this error).
[...]
> ! # error there are some unknown limits. Fixme!
> --- 3535,3541 ----
> ! there are some unknown limits. Fixme!
Actually the usually preferred way to do #error is thus:
#if SOME_PROBLEMATIC_CONDITION
#error Fix me.
#endif
This works because K&R preprocessors don't recognise preprocessor
directives unless the # is in column 1. In this case, they would pass
the "#error Fix me." text through to the compiler, which will barf just
as it would without the "#error". The advantages of this technique are
(1) ANSI compilers will abort properly, and (2) it makes it clearer
that this is intended to abort compilation.
-zefram
next prev parent reply other threads:[~1996-05-08 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199605070206.EAA26805@jagor.srce.hr>
1996-05-07 20:39 ` Zoltan Hidvegi
1996-05-08 14:54 ` Zefram [this message]
1996-05-06 22:54 Hrvoje Niksic
1996-05-07 1:23 ` Zoltan Hidvegi
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=3061.199605081454@stone.dcs.warwick.ac.uk \
--to=a.main@dcs.warwick.ac.uk \
--cc=hniksic@public.srce.hr \
--cc=hzoli@cs.elte.hu \
--cc=zsh-workers@math.gatech.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).