Mail Archives: djgpp/1996/03/21/20:34:29
Xref: | news2.mv.net comp.os.msdos.djgpp:2029
|
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: typedefs
|
Date: | Thu, 21 Mar 1996 18:13:13 +0200
|
Organization: | NetVision LTD.
|
Lines: | 18
|
Message-ID: | <Pine.SUN.3.91.960321181041.25389G-100000@is>
|
References: | <4i1ctq$neh AT nntp DOT crl DOT com>
|
NNTP-Posting-Host: | is.elta.co.il
|
Mime-Version: | 1.0
|
In-Reply-To: | <4i1ctq$neh@nntp.crl.com>
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
On Mon, 11 Mar 1996, Weiqi Gao wrote:
> I noticed that the following line of code
> typedef asdf long;
> causes a compiler error in gcc. I checked the documentation and sure
Of course it's an error. You should have said this:
typedef long asdf;
> enough, "typedef" means something completely different in gcc than in
> standard C compilers. Is there a way to let typedef do the standard
> thing?
You've read it wrong, `typedef' in gcc does the same that it does in any
other compiler. `typedef' is an ANSI-standard feature and gcc is
ANSI-compliant compiler.
- Raw text -