Mail Archives: djgpp/2000/10/20/11:01:55
From: | see DOT sig AT for DOT email DOT address (Peter B. Steiger)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Typedefs for Dummies
|
Organization: | None whatsoever
|
Message-ID: | <39f05c8e.3570804@netnews.att.net>
|
X-Newsreader: | Forte Free Agent 1.21/32.243
|
Lines: | 23
|
Date: | Fri, 20 Oct 2000 14:54:16 GMT
|
NNTP-Posting-Host: | 63.11.71.230
|
X-Complaints-To: | abuse AT worldnet DOT att DOT net
|
X-Trace: | bgtnsc07-news.ops.worldnet.att.net 972053656 63.11.71.230 (Fri, 20 Oct 2000 14:54:16 GMT)
|
NNTP-Posting-Date: | Fri, 20 Oct 2000 14:54:16 GMT
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Reply-To: | djgpp AT delorie DOT com
|
Can somebody translate this to English for me? I grew up on Pascal
and went from there to Clipper where I earn a living, so I have never
been able to wrap my mind around C syntax. 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:
typedef unsigned char BYTE;
typedef BYTE far *BYTEP;
typedef BYTEP PBYTE;
What the heck does that mean, and why doesn't gcc like it?
The platform is a PIII running NT 4.0, if that makes a difference.
Peter B. Steiger
Cheyenne, WY
----
If you reply by email, send it to pbs at com dot
canada (or vice-versa). All advertisements will be
returned to your postmaster, eh!
- Raw text -