Migration from Sun solaris 8 to Solaris 10

Question

Hi,
We are migrating from Solaris 8 to Solaris 10 with the compiler migration also earlier we are using Sun Studio 6 and now it is Sun Studio 11.
When we are compiling the code on Solaris 10 which has been running on the Solaris 8, we are facing some error. So could you help me on this
"ResourceManager.h", line 98: Warning (Anachronism): Type names qualified by template parameters require "typename".
"ConnectionMgr.h", line 62: Where: While specializing "ResourceManager<T>".
"ConnectionMgr.h", line 62: Where: Specialized in non-template code.
"ResourceManager.h", line 100: Warning (Anachronism): Type names qualified by template parameters require "typename".
"ConnectionMgr.h", line 62: Where: While specializing "ResourceManager<T>".
"ConnectionMgr.h", line 62: Where: Specialized in non-template code.
2 Warning(s) detected.
make[1]: *** [obj/ConnectionMgr.o] Error 2
Not sure of the warning , am not able to see these error on the compilation on Sun Studio 6.Below is the bit of the header file code, where the error is occurring.
98 typedef map<ResourceID, ResElement *>::iterator ResMapIterator;
100 typedef list<ResElement *>::iterator ResListIterator;
We are using a /opt/SUNWspro/bin/CC compiler and the verison is CC: Sun C++ 5.8
Please help me out about the issue

Answer 1

Since you are jumping several compiler releases and two Solaris releases, you should migrate in two steps.
1. Get your application working with Sun Studio 11 on Solaris 8.
2. You can now run that application on Solaris 10, or you can rebuild it on Solaris 10 and then run it.
An application built on Solaris 8 will run on Solaris 9 and 10.
An application built on Solaris 10 cannot be run on Solaris 8 or 9.
We promise upward binary compatibility, allowing an old binary to be used with a newer compiler or on a newer Solaris. But we can't promise source code compatibility because we don't want to have to duplicate old bugs in old compilers.
C++ 5.8 in Sun Studio 11 detects errors that older compilers might have missed. The rules about where to use "typename" are one example.
I would not expect the warning about typename to be generated by either of the source code lines that you show, but I can't really tell without seeing a compilable example.
You need to use typename when you use a type that depends on a template parameter. Example:
template <class T> class C1 {
public:
    typedef T Type;
template <class T> class C2 {
public:
    typename T::Type a;
C2< C1<int> > c2i;If in C2 you do not specify typename, the compiler does not know whether T::Type is intended to be the name of a type. If it is not a type, the code is always invalid. The C++ rule is that if an an identifier is not known to be a type, it is not a type. You use typename to tell the compiler that T::Type is supposed to be the name of a type.