Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!sdcsvax!sdchem!tps
From: tps@sdchem.UUCP
Newsgroups: comp.lang.c
Subject: #define escape newline
Message-ID: <648@sdchema.sdchem.UUCP>
Date: Sat, 14-Mar-87 05:30:09 EST
Article-I.D.: sdchema.648
Posted: Sat Mar 14 05:30:09 1987
Date-Received: Sat, 14-Mar-87 19:38:43 EST
Sender: news@sdchem.UUCP
Reply-To: tps@sdchem.UUCP (Tom Stockfisch)
Distribution: na
Organization: UC San Diego
Lines: 29


I always define my functions according to the Indian Hill style sheet; that is,
with the type on one line, and the function identifier on a separate one, as in

struct foo *
func( arg )
{
	...
}

The major advantage of this layout is that the definition is easy to find in
the text editor ( /^func/ ).

Now recently I had the (I thought brilliant) notion to do the same thing with
macro function definitions.  Like this:

# define \
Func( arg )	...

Only now my compiler says

	illegal macro name
	missing endif

Which is broken, my usage or my compiler?

Is this yet another subtlety the ANSI committee has to worry about?

|| Tom Stockfisch, UCSD Chemistry	tps%chem@sdcsvax.UCSD