Message-ID: <39F0F704.D21E450B@user.rose.com>
From: April <awhite AT user DOT rose DOT com>
X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {TLC;RETAIL}  (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Typedefs for Dummies
References: <39f05c8e DOT 3570804 AT netnews DOT att DOT net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 27
Date: Fri, 20 Oct 2000 20:53:08 -0500
NNTP-Posting-Host: 205.189.215.11
X-Trace: client 972089127 205.189.215.11 (Fri, 20 Oct 2000 20:45:27 EDT)
NNTP-Posting-Date: Fri, 20 Oct 2000 20:45:27 EDT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

"Peter B. Steiger" wrote:

> This week I'm trying to
> write a C module to link in with my Clipper program, and the Clipper
> headers required for such a project make some definitions that were
> apparently written for the Evil Empire's compiler; gcc gags on them
> with "Parse error before *".  Here's an example:

Unless I am very mistaken, a C module written for gcc will not work with
Clipper (which I use as well for work).

Unless the .o format is the same as the micro$oft .obj, it will not link.

Either msc6.0 or borland c4.5 (around there) will work.

BTW, even bc4.5 will not work if the C module involved floating point
numbers.

If you need to, and it is small, please email me the C code directly;
I'll send
you msc6.0 compiled .obj back

As well, are you no reading comp.lang.clipper where this question may
have been more appropriate?

April