Sun Forte c++ config in cvs

From: Gennadiy E. Rozental (rogeeff_at_[hidden])
Date: 2001-10-18 09:44:27

Hi,

I am looking onto latest sunpro config located in cvs:

#    if (__SUNPRO_CC <= 0x520)
       //
       // Sunpro 5.3 and later: 

!! I think that 0x520 marks version 5.2. Is it correct comment?

       //
       // although sunpro 5.3 supports the syntax for
       // inline initialization it often gets the value
       // wrong, especially where the value is computed
       // from other constants (J Maddock 6th May 2001)
#      define BOOST_NO_INCLASS_MEMBER_INITIALIZATION
       // although sunpro 5.3 supports the syntax for
       // partial specialization, it often seems to
       // bind to the wrong specialization.  Better
       // to disable it until suppport becomes more stable
       // (J Maddock 6th May 2001).
#      define BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION
#    endif

#    if (__SUNPRO_CC <= 0x530) || !defined(BOOST_STRICT_CONFIG)
       // integral constant expressions with 64 bit numbers fail
#      define BOOST_NO_INTEGRAL_INT64_T
#    endif

So it seems that we starting to use partial class specialization for 
sunpro compiler now. I support this decision. After some testing I 
was able to compile most of the libraries. iterator_adaptors still 
need some tuning to make it work (almost - complex tests still do not 
pass). After that tokenizer start working. 
  It seems that we still define BOOST_NO_STD_ITERATOR_TRAITS with 
native stl because RW defines flag _RWSTD_NO_CLASS_PARTIAL_SPEC. Is 
there a way to turn in off?

Gennadiy.