Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!mcvax!hp4nl!eutrc3!wzv!wietse
From: wietse@wzv.UUCP (Wietse Z. Venema)
Newsgroups: comp.lang.c
Subject: Re: Optional semi-colons
Message-ID: <292@wzv.UUCP>
Date: 1 May 89 20:57:06 GMT
References: <41117@oliveb.olivetti.com> <225800165@uxe.cso.uiuc.edu>
Reply-To: wietse@wzv.UUCP (Wietse Z. Venema)
Organization: Eindhoven University of Technology, The Netherlands
Lines: 15

Arguing why \n should not terminate C statements where syntax permits, I wrote:
>For example, the C preprocessor. Having a unique statement terminator frees
>the programmer of worrying where newlines might show up after macro expansion.

mcdonald@uxe.cso.uiuc.edu (Doug McDonald) writes:
>Really? What happens if macro expansion results in a string longer
>than 509 characters, or an expression several thousands of bytes long?
>I have had both of those happen. Serious worries result.

You will have to insert some extra newlines into the source.  My point
is that you won't have to worry about prematurely terminated statements.
-- 
work:	wswietse@eutrc3.uucp	| Eindhoven University of Technology
work:	wswietse@heitue5.bitnet	| Mathematics and Computing Science
home:	wietse@wzv.uucp		| Eindhoven, The Netherlands