On Monday 28 of April 2003 19:40, Marcus Camen wrote:
> > On Monday 28 April 2003 19:18, Marcus Camen wrote:
> > >-    ifstream f(QFile::encodeName(m_file));
> > >+    std::ifstream f(QFile::encodeName(m_file));
> >
> > I know you just made it compile, but, uhm, this should really be QTL,
> > shouldn't it?
>
> Yes, of course. If we would nuke all STL code in KDE we would get rid of
> about 60-70 % of all compile problems on non-gcc compilers. But I don't
> want to rewrite all that code myself...  ;-)
> ... and we probably don't want such rewrites in the BRANCH.

 I remember using ifstream ten years ago (ok, that was a slightly different 
one I guess). What kind of problems should there be with it?

 In fact, now that we have here the STL discussion, what problems in general 
do non-gcc compilers have with STL? Well, besides the compiler being quite 
old, but I thought KDE already demands quite capable C++ compiler that should 
be able to handle at least common usage of STL?

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak@suse.cz , l.lunak@kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/