>>>>> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> Andre'> Nope... but my compiler does not like the 'std::' stuff in
>> Andre'> src/encoding anyway... *sniff*
Asger> Ok, here's a recipe for avoiding "std::" compilation errors.
Asger> I'm not sure we want to follow this, but in case we decide to
Asger> have gcc 2.7.2 support, this is how we could do it:
Asger> 1. Add "using std::XXX;" at the beginning of a file that
Asger> complains about std::XXX. 2. Change all "std::XXX" to "XXX" in
Asger> the rest of the file.
I'm not sure whether 2.7.2 supports using. In any case, the NEWS file
for 2.8.1 says:
* Standard usage syntax for the std namespace is supported; std is treated
as an alias for global scope. General namespaces are still not supported.
Do we really need these 'using' statements now, except that they are
the ANSI way of doing things? Are there compilers that will fail to
find string and wstring if std:: is not explicitely given?
Asger> If you have a native compiler, please try to compile the
Asger> development version and tell us about any problems.
I think I will have a lot of work to get it going with DEC cxx. I'll
submit my findings to the list before doing changes to bring back
compatibility.
Asger> Then we can better judge whether it's fair to drop support for
Asger> gcc 2.7.2 in case it's the only one that requires these work
Asger> arounds.
Right. I think we should *try* to support the latest versions of the
vendor-provided compiler.
JMarc
