Xref: utzoo comp.unix.xenix:4587 comp.lang.c:15711
Path: utzoo!utgpu!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!agate!bionet!csd4.milw.wisc.edu!leah!itsgw!rpi!sun.soe.clarkson.edu!batcomputer!cornell!rochester!pt.cs.cmu.edu!cadre!pitt!darth!libove!root
From: root@libove.UUCP (Jay M. Libove)
Newsgroups: comp.unix.xenix,comp.lang.c
Subject: Problem with strange macro definition
Message-ID: <208@libove.UUCP>
Date: 21 Jan 89 17:13:39 GMT
Organization: Libove, Pittsburgh, PA, U.S.A.
Lines: 29


System: SCO Xenix 286 v2.2.1 (roughly System V release 2 Unix) on a
PCs Limited 286 box; SCO Xenix 286 v2.2.1 development system as well.

I am trying to build a huge software package that includes something
like this:

#define awful_macro(nnnn) \
 if (x_/**/nnnn > y_/**/nnnn) z_/**/nnnn = 0

Which causes the SCO compiler to generate errors claiming that
x_nnnn y_nnnn and z_nnnn are undefined variables in the source module.

I know that it is a long standing and not-likely-to-be-corrected bug
in the generic 'pcc' compiler that makes x_/**/nnnn evaluate to x_nnnn
instead of the x_ nnnn that the language definition calls for it to be,
and I can only assume that the authors of this gross code intended for
macro substitution to take place on the nnnn part, achieving the effect
of passing multiple variables via one name... but anyway it certainly
doesn't work.

Can someone suggest what to do to get around this?

Thanks in advance!
-- 
Jay Libove		ARPA:	jl42@andrew.cmu.edu or libove@cs.cmu.edu
5731 Centre Ave, Apt 3	BITnet:	jl42@andrew or jl42@drycas
Pittsburgh, PA 15206	UUCP:	uunet!nfsun!libove!libove or
(412) 362-8983		UUCP:	psuvax1!pitt!darth!libove!libove