Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site sjuvax.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!psuvax1!burdvax!sjuvax!jss
From: jss@sjuvax.UUCP (J. Shapiro)
Newsgroups: net.lang.c
Subject: Re: C-Debug package ... (a la "context-independent macros")
Message-ID: <802@sjuvax.UUCP>
Date: Tue, 5-Feb-85 02:15:23 EST
Article-I.D.: sjuvax.802
Posted: Tue Feb  5 02:15:23 1985
Date-Received: Fri, 8-Feb-85 00:45:47 EST
References: <1885@wateng.UUCP> <1089@hcrvx1.UUCP> <33@daisy.UUCP> <1097@hcrvx1.UUCP> <1924@wateng.UUCP>
Organization: Saint Josephs Univ. Phila., Pa.
Lines: 29

[Aren't you hungry...]

In article <33@daisy.UUCP> pkl@daisy.UUCP (Peter K. Lee) writes:
>	# define macro(args)\
>		if (1) {\
>			/* macro body */\
>		}\
>		else
Kevin Szabo points out that:
>	macro( args )
>	next_statment;
fails in this macro, and is hard to find.  If, hoever, one writes

	else;

instead of

	else

the problem goes away.

Personally I still like my macros simple. I favor the notion of intelligent
compilation and elimination of redundant/unused object modules as more
valuable then #define'd pseudofunctions.

If only there were a way to say "now about this function - it goes inline"
in C. It's been done in Franz Lisp - take a look at defmacro....
Any volunteers? :-)