Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!munnari.oz.au!bruce!cechew
From: cechew@bruce.cs.monash.OZ.AU (Earl Chew)
Newsgroups: comp.os.minix
Subject: Re: Problem with cppmake for 1.5.10
Message-ID: <3397@bruce.cs.monash.OZ.AU>
Date: 27 Nov 90 00:49:53 GMT
References: <1447@sun13.scri.fsu.edu> <3390@bruce.cs.monash.OZ.AU> <1904@Terra.cc.brunel.ac.uk>
Organization: Monash Uni. Computer Science, Australia
Lines: 44

In <1904@Terra.cc.brunel.ac.uk> eesrajm@cc.brunel.ac.uk (Andrew J Michael) writes:

>This doesn't actually seem to be the problem, unless I've got a different 
>problem to everyone else :-)

Hmm... the latter :-(

>My error message reads 

>"cppmake.c", line 1167: unbalanced parenthesis
>"cppmake.c", line 1218: unterminated macro call
>"cppmake.c", line 1218: (warning) argument mismatch, F1V
	[.. lots of diagnostics ..]

The offending code is:

void appendarg F1V(PROCESS *, p,

{
  VA_LIST, ap,				/* point at argument list */
  char *q;				/* point at argument */

  VA_START(ap, p);)

  [.. code deleted ..]
}

I don't know which cpp you're using. The problem seems to be that your cpp
gives up collecting macro arguments at \n just after "PROCESS *, p,".

The reason the code is written this way is to allow ANSI-style argument
declarations while allowing compilation under old-style compilers, and
also using varargs.h *or* stdarg.h. The strange parenthesis nesting allows
me to still use '%' in vi to match parentheses.

Try running cpp only on the file to see whether it's because your cpp gives
up the the \n. I have compiled this successfully using ack, bcc, gcc, Pyramid
cc and Sun cc.

Earl
-- 
Earl Chew, Dept of Computer Science, Monash University, Australia 3168
EMAIL: cechew@bruce.cs.monash.edu.au PHONE: 03 5655447 FAX: 03 5655146
----------------------------------------------------------------------