Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!caip!andromeda!njitcccc!ken
From: ken@njitcccc.UUCP (Kenneth Ng)
Newsgroups: net.lang.c
Subject: Re: What should be added to C
Message-ID: <171@njitcccc.UUCP>
Date: Fri, 30-May-86 23:04:46 EDT
Article-I.D.: njitcccc.171
Posted: Fri May 30 23:04:46 1986
Date-Received: Sun, 1-Jun-86 07:47:23 EDT
References: <1462@mmintl.UUCP> <5498@alice.uUCp> <2823@utcsri.UUCP> <963@h-sc2.UUCP>
Organization: NJ Inst of Tech., Newark NJ
Lines: 26

In article <963@h-sc2.UUCP>, augart@h-sc2.UUCP (augart) writes:
> >>> o The ability to define multi-line pre-processor macros, using #begdef and
> >>> #enddef statements.  #if and other conditionals in the body of the
> >>> definition would be evaluated when the macro was not interpreted, not when
> >>> it is encountered.
> >>Why would you want to use it?
> >When your macro won't fit on a line, and/or you want to use #if's etc
> >as part of the macro, obviously. 
> 
> If your macro won't fit on a line, you can already handle this problem by
> finishing off each line except the last with a backslash.
> The other addition would be a win, though.
C will not allow you to put #if's into a multiple line
macro, the backslash only allows you to continue the same line
on the next line.  It does NOT allow you to start another line.

-- 
Kenneth Ng: uucp(unreliable) ihnp4!allegra!bellcore!njitcccc!ken
	    bitnet(prefered) ken@njitcccc.bitnet

New Jersey Institute of Technology
Computerized Conferencing and Communications Center
Newark, New Jersey 07102

Vulcan jealousy: "I fail to see the logic in prefering Stonn over me"
Number 5: "I need input"