When I build ORE-SWIG in the latest version ORE-Engine( master release ) with VS2022, and SWIG 4.3.0, I got lots of C2275 type errors like “std::map<....>::iterator”: expected an expression instead of a type。and then the building was terminated. I have learned that when SWIG generates wrapper code, if it fails to automatically add the typename keyword to nested template types, compiler errors will occur. So I can add "typename" before std::map<...>::iterator, e.g. SwigValueWrapper<typename std::map< enum CurveSpec::CurveType,std::set< std::string > >::iterator > in oreanalyticsPYTHON_wrap.cxx, but it is cumbersome,and time-consuming to fix one by one. I wonder if this is caused by inconsistent versions in SWIG and ORE_SWIG? can anybody help , thanks.
When I build ORE-SWIG in the latest version ORE-Engine( master release ) with VS2022, and SWIG 4.3.0, I got lots of C2275 type errors like “std::map<....>::iterator”: expected an expression instead of a type。and then the building was terminated. I have learned that when SWIG generates wrapper code, if it fails to automatically add the typename keyword to nested template types, compiler errors will occur. So I can add "typename" before std::map<...>::iterator, e.g. SwigValueWrapper<typename std::map< enum CurveSpec::CurveType,std::set< std::string > >::iterator > in oreanalyticsPYTHON_wrap.cxx, but it is cumbersome,and time-consuming to fix one by one. I wonder if this is caused by inconsistent versions in SWIG and ORE_SWIG? can anybody help , thanks.