delorie.com/archives/browse.cgi | search |
From: | "Martin Ambuhl" <mambuhl AT tiac DOT net> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Trouble with many mallocs and reallocs |
Date: | Tue, 11 Aug 1998 20:50:47 -0400 |
Organization: | Nocturnal Aviation |
Lines: | 20 |
Message-ID: | <6qqooa$7v@news-central.tiac.net> |
References: | <Pine DOT SUN DOT 3 DOT 91 DOT 980810093926 DOT 1429A-100000 AT is> <35cf519a DOT 8496651 AT news3 DOT newscene DOT com> <35D0A962 DOT FCE5C718 AT unb DOT ca> |
NNTP-Posting-Host: | p43.tc1.newyo.ny.tiac.com |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Endlisnis wrote in message <35D0A962 DOT FCE5C718 AT unb DOT ca>... |Bruno Barberi Gnecco wrote: | |> struct node { |> struct node *forward, *back; |> unsigned char *data; |> }; |> typedef struct node NODE; | | Why do you use a typedef to reference 'node' as 'NODE'? |node a; //SAME AS |NODE a; | I don't have the original post handy, but if he is writing C, your construction is illegal. If he is writing C++, his construction is illegal.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |