Xref: utzoo comp.unix.questions:6370 comp.lang.c:8796
Path: utzoo!utgpu!water!watmath!clyde!att-cb!att-ih!pacbell!ames!mailrus!tut.cis.ohio-state.edu!lvc
From: lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani)
Newsgroups: comp.unix.questions,comp.lang.c
Subject: Re: 3B2 cpp #ifdef + #include
Keywords: cpp 3B2 #ifdef #include
Message-ID: <9538@tut.cis.ohio-state.edu>
Date: 3 Apr 88 13:11:55 GMT
References: <109@iquery.UUCP> <2023@pasteur.Berkeley.Edu> <17983@watmath.waterloo.edu>
Organization: The Ohio State University Dept of Computer and Information Science
Lines: 20

In article <17983@watmath.waterloo.edu> rbutterworth@watmath.waterloo.edu (Ray Butterworth) writes:
>> 
>They bother because it is nice to be warned if you entered something
>that looks like it means something but doesn't.  There is nothing
>worse (well not really) than software that silently ignores input that
>it doesn't understand.

You are right of course.  This is such a widely used idiom
though that cpp should be changed to allow it.  I heard ATT-IS
(or whatever its called these days) changed cpp to allow tokens
after the closing # directives as long as it (they?) was an
exact match with the corresponding opening # directive.  But,
incredibly it would complain about comments after the # directives!
This is so stupid!  Maybe I should sell my AT&T stock.  Sigh.
Is anyone at ATT-IS listening that would care to admit to
this botch if it is true?
-- 
Larry Cipriani, AT&T Network Systems and Ohio State University
Domain: lvc@tut.cis.ohio-state.edu
Path: ...!cbosgd!osu-cis!tut.cis.ohio-state.edu!lvc (weird but right)