From: "Tim 'Zastai' Van Holder" Newsgroups: comp.lang.c++,comp.os.msdos.djgpp References: <4j%t5.6782$vo6 DOT 96767 AT news2-win DOT server DOT ntlworld DOT com> Subject: Re: passing istringstream as istream in param Lines: 27 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: Date: Fri, 08 Sep 2000 20:57:18 GMT NNTP-Posting-Host: 213.224.93.143 X-Trace: afrodite.telenet-ops.be 968446638 213.224.93.143 (Fri, 08 Sep 2000 22:57:18 MET DST) NNTP-Posting-Date: Fri, 08 Sep 2000 22:57:18 MET DST Organization: Pandora - Met vlotte tred op Internet To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Mostyn Lee" wrote in message news:UX%t5.105$t42 DOT 4862 AT nsw DOT nnrp DOT telstra DOT net... > thanks john, but i think you misunderstand my problem, which is not with the > generated code, merely with the interface to that code. I cant get my > character string in the form of istream * for the lexer to do its parse. No he doesn't. The problem is that flex generates C(++) code targeted mainly for the GNU compiler, which doesn't have an STL iostream yet (well, not in the official distribution anyway). Microsoft does have this. A solution might be to include iostream at the top of your flex input file, and possibly adding typedef basic_iostream > iostream; there as well. If, as John suspects, M$VC also has an iostream.h defining an iostream class, things could get trickier. In that case, you're better off changing the flex skeleton (by including iostream instead of iostream.h if WIN32 is defined, for example) and recompiling flex. -- Hi, I'm a signature virus. plz set me as your signature and help me spread :)