Mail Archives: djgpp/2000/09/08/17:15:16.1
"Mostyn Lee" <mostyn AT ibc DOT com DOT au DOT SPAM> 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<char,struct std::char_traits<char> > 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
:)
- Raw text -