Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site pegasus.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!pegasus!hansen
From: hansen@pegasus.UUCP (Tony L. Hansen)
Newsgroups: net.lang.c
Subject: Re: ANSI C preprocessor
Message-ID: <2623@pegasus.UUCP>
Date: Sat, 5-Oct-85 17:55:39 EDT
Article-I.D.: pegasus.2623
Posted: Sat Oct  5 17:55:39 1985
Date-Received: Sun, 6-Oct-85 07:10:36 EDT
References: <858@lll-crg.UUCP> <201@rtp47.UUCP>
Reply-To: hansen@pegasus.UUCP (60545451-Tony L. Hansen;LZ 3B-315;6243)
Distribution: net
Organization: AT&T Information Systems, Lincroft NJ
Lines: 24
Keywords: System V.2
Summary: not in all Vr2's

In article <201@rtp47.UUCP> meissner@rtp47.UUCP (Michael Meissner) writes:
< In article <858@lll-crg.UUCP> brooks@lll-crg.UUCP (Eugene D. Brooks III) writes:
< >Has anyone out there in netland implemented the #elif preprocessor
< >directive of the proposed ANSI standard in Reiser's preprocessor?
< 
< The System V.2 preprocessor has the #elif construct (which is where it came
< from).

When the #elif construct was officially accepted by the AT&T C Standards
committee, it was too late to get it into the System Vr2 UNIX which was
going onto Vaxen and 3B-20's.  It was then added to the Vr2 C compiler which
came out later on the 3B-2's and 3B-5's.  I don't know about its existence
on other Vr2 ports, except the Amdahl, which does not have it.

Since it was already a part of AT&T's C standard by the time the ANSI
committee started up, it was added with almost no comment.

The ideas of #elifdef and #elifndef were also debated and rejected by AT&T's
committee.  (#elifdef was defeated mostly because of strong objections to
the four-word contraction in #elifndef, and the feeling that if one came in,
then both should come in.)

					Tony Hansen
					ihnp4!pegasus!hansen