Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles; site uokvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!inuxc!pur-ee!uiucdcs!parsec!ctvax!uokvax!emjej
From: emjej@uokvax.UUCP
Newsgroups: net.lang.c
Subject: Re: "missing endif": Huh?Who?What? - (nf)
Message-ID: <3000023@uokvax.UUCP>
Date: Thu, 26-Apr-84 10:15:00 EDT
Article-I.D.: uokvax.3000023
Posted: Thu Apr 26 10:15:00 1984
Date-Received: Sun, 29-Apr-84 07:08:54 EDT
References: <13900001@acf4.UUCP>
Lines: 22
Nf-ID: #R:acf4:-1390000100:uokvax:3000023:000:637
Nf-From: uokvax!emjej    Apr 26 09:15:00 1984

#R:acf4:-1390000100:uokvax:3000023:000:637
uokvax!emjej    Apr 26 09:15:00 1984

/***** uokvax:net.lang.c / acf4!lwe3207 /  6:44 am  Apr 22, 1984 */
The following file elicits the interesting response "missing endif" from cc.
Replacing *v/*w with (*v)/(*w) fixes it:

---
foo (v,w)
int *v, *w;
{	int k;
	k = *v/*w;		}
---
/* ---------- */

The preprocessor thinks that the /* in *v/*w is the beginning of a comment,
and eliminates the rest of the code. I don't know why the "missing endif"
shows up; indeed, the version of the C compiler I had the misfortune to use
a while back didn't give a missing endif message, and cheerfully passed on
an empty file to the C compiler, which didn't mind a bit.

						James Jones