> Andre'> Nope... but my compiler does not like the 'std::' stuff in
> Andre'> src/encoding anyway... *sniff*
Ok, here's a recipe for avoiding "std::" compilation errors.
I'm not sure we want to follow this, but in case we decide to
have gcc 2.7.2 support, this is how we could do it:
1. Add "using std::XXX;" at the beginning of a file that
complains about std::XXX.
2. Change all "std::XXX" to "XXX" in the rest of the file.
I have not tested whether this helps, but at least we will
be able to isolate the problem to the "using" statement
then.
And "using" statements can be surrounded by #ifdefs, because
they are not needed on these obsolete compilers.
If you have a native compiler, please try to compile the
development version and tell us about any problems.
Then we can better judge whether it's fair to drop support
for gcc 2.7.2 in case it's the only one that requires these
work arounds.
Greets,
Asger
