Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-lcc!lll-winken!uunet!ficc!peter
From: peter@ficc.uu.net (Peter da Silva)
Newsgroups: comp.lang.c
Subject: Re: Statement terminators
Message-ID: <4123@ficc.uu.net>
Date: 9 May 89 13:36:10 GMT
References: <41117@oliveb.olivetti.com> <225800165@uxe.cso.uiuc.edu> <1843@ubu.warwick.UUCP>
Organization: Xenix Support
Lines: 27

In article <1843@ubu.warwick.UUCP>, geoff@cs.warwick.ac.uk (Geoff Rimmer) writes:
> In article <2296@mit-caf.MIT.EDU> vlcek@mit-caf.MIT.EDU (Jim Vlcek) writes:
> > In fact, I myself would lean the other direction and prefer that
> > macros not follow the strict ``to the next newline'' rule, but rather
> > have a more explicit means of terminating the definition body.

Me too...

> I agree that it can be *very* annoying having to backquote all the
> newlines in macros (take a look at "putc" in stdio.h !)  But how else
> could cpp be designed so it knows when to stop?

A new construct for multiline macros?

#begin Malloc(x)
	({char *tempptr=malloc(x);
		if (!tempptr) perror_("malloc failed");tempptr;})
#end

> (BTW this is only when I'm using gcc - so no flames!)

I think it's kind of cute, but then I get nostalgic over BCPL.
-- 
Peter da Silva, Xenix Support, Ferranti International Controls Corporation.

Business: uunet.uu.net!ficc!peter, peter@ficc.uu.net, +1 713 274 5180.
Personal: ...!texbell!sugar!peter, peter@sugar.hackercorp.com.