Date: Thu, 19 Mar 1998 17:49:19 -0800 (PST) Message-Id: <199803200149.RAA14439@adit.ap.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: unjl AT ab272 DOT rz DOT uni-karlsruhe DOT de (Johannes Dieterich), djgpp AT delorie DOT com From: Nate Eldredge Subject: Re: Help me please Precedence: bulk At 05:57 3/18/1998 GMT, Johannes Dieterich wrote: >Johannes Dieterich (unjl AT ab272 DOT rz DOT uni-karlsruhe DOT de) wrote: >> Hi there. > >> Trying to compile bar.cc I encountered the following errors: >[Rest snipped] > > >he he he >Seems I'm replying to my own post. Two hours after starting this thread >(half an hour spent in front of the computer) I've identified the problem. >It occurs whenever you include (or or any other lib that uses >) and in the same compilation unit AND is >included before . >The reason is, the operator deklarations the error messages refer to in > (included somehow from ) somehow match the operators in > in an inproper way. >But if you include before anything goes fine and the >template instantiation is not ambiguous. This is a little weird. Could somebody who knows more C++ than me decide whether this is a reasonable thing for the compiler to barf on? > >Does'nt matter. The workaround works around. That's what I'm afraid of. :\ A workaround is fine, for you, but it doesn't help it get fixed for the future. >What I would be interested in: Does this error occur also in other >C++-Compilers ? A good question, but I don't have any other ones to try. Nate Eldredge eldredge AT ap DOT net