Subj : stl  and _USE_OLD_RW_STL
To   : borland.public.cpp.borlandcpp
From : grahamo
Date : Fri Sep 16 2005 03:12 am


Hi, 

cpp builder 6


I've already posted this to the ide forum but I think this is the correct place for my question. Apologies for cross posting. 

I have an app that is already built and deployed in prod. It uses corba and is therefore compiled with the _USE_OLD_RW_STL option (the compiler requires that apparently as the visibroker stuff was compiled with the old rw tools).
 

Now I have written custom iterators which I have tested and are functional. I need to integrate them into the code now however I am getting all sorts of errors at compile time because (I think) of the _USE_OLD_RW_STL option. The errors I'm seeing are down in the likes of;


(note the "oldstl" in the path below).....

Error E2285 C:\PROGRA~1\Borland\CBUILD~1\Bin\..\include\oldstl\algorith.h 695: Could not find a match for 'std::__value_type<Category,T,Distance,Pointer,Reference>(contIter<TtkDouble>)' in function void __quick_sort_loop<contIter<TtkDouble>,compareLess<TtkDouble> >(contIter<TtkDouble>,contIter<TtkDouble>,compareLess<TtkDouble>)
 + Full parser context
 + C:\PROGRA~1\Borland\CBUILD~1\Bin\..\include\oldstl\algorith.h, line 694: decision to instantiate: void void __quick_sort_loop<contIter<TtkDouble>,compareLess<TtkDouble> >(contIter<TtkDouble>,contIter<TtkDouble>,compareLess<TtkDouble>)


Not very pretty, eh ? ;) I haven't delved (I'd rather not have to debug obsolete/non-standard code to be honest) but I suspect this is due to different definitions of iterators and their contents for the old RW stl. 


anyways, I'd like to know if I'm obliged to use the old stl stuff (via the _USE_OLD_RW_STL flag) or is there anyway I can use the standard stl in the app. There's CORBA in this application so I can't just pull the _USE_OLD_RW_STL flag/definition from the compiler. At the same time I don't want to use the old roguewave stuff. 

Any tips/ideas? 

Cheers

Graham

.