Path: utzoo!attcan!uunet!husc6!think!bloom-beacon!gatech!udel!princeton!phoenix!haahr
From: haahr@phoenix.Princeton.EDU (Paul Gluckauf Haahr)
Newsgroups: comp.lang.c
Subject: comments before preprocessor directives
Summary: #/* foo */define and /* foo */#define
Keywords: cpp
Message-ID: <2873@phoenix.Princeton.EDU>
Date: 13 May 88 01:17:59 GMT
Reply-To: haahr@princeton.edu (Paul Gluckauf Haahr)
Organization: Princeton University, NJ
Lines: 21

what is an ansi compliant c preprocessor supposed to do with

	#/*foo*/define	x y
	x

or

	/*foo*/#define	x y
	x

the preprocessor that is shipped with sun os 3.5 gives y for the first
case and x for the second.  i would assume this is probably the same
behavior as most reiser-derived preprocessors, which probably accounts
for the bulk of unix preprocessors.  how do other machines handle it
now?

and has anyone ever used code like that for a good reason?  has anyone
even seen any code which counts on one or the other behavior?

paul haahr
princeton!haahr (haahr@princeton.edu)