Mail Archives: djgpp/1996/08/19/01:16:26
Xref: | news2.mv.net comp.os.msdos.djgpp:7603
|
From: | Ian Miller <itmiller AT dra DOT hmg DOT gb>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: Add this to FAQ: <complex> and <string> must be #included before STL!
|
Date: | Fri, 16 Aug 1996 13:02:41 +0100
|
Organization: | DRA HASN
|
Lines: | 33
|
Message-ID: | <32146361.41C67EA6@dra.hmg.gb>
|
References: | <4v18br$ev2 AT jaxnet DOT southeast DOT net>
|
NNTP-Posting-Host: | 146.80.115.106
|
Mime-Version: | 1.0
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
M. Edward Kiser wrote:
>
> <complex> and <string> must be #included before STL.
>
> I found this out in a huge program and couldn't find the bug so I made
> a copy and started deleting stuff to see when the bug would go away. I
> eventually got to this, and the bug was still there:
>
> #include <list>
> #include <complex>
> #include <string>
>
> So I rearranged the includes
>
> #include <complex>
> #include <string>
> #include <list>
>
> and the bug went away.
>
> I didn't see this in the FAQ or the INFO anywhere. Maybe I missed it.
It looks like a bug to me. Perhaps there is some redefinition
going on; the same macros being used by different header files
in incompatible ways. I don't believe this rearrangement is necessary
for properly written code.
Let's have some details about the bug so that we can get a real
solution rather than the above workaround.
--
Ian Miller, AFRICA (DORSET), UK
DJGPP 2.00, Win95 DOS box (LFN=n), 486DX4/100, 24Mbytes RAM
- Raw text -