Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 313
  • Last Modified:

STL and MSVC++ v5.0 colide at iostream

I am using STL (MSDEV) with the Microsoft Visual C++ Ver 5.0, and since it was introduced to my project I have problems with things like fopen and stuff. I tried to look deeper in the process, and found out that lower-level functions still work - _open returns a handler, but the upper level fopen receives a NULL.
I looked through the available net documentation about the MSVC++ and STL (actually for ver 4.2 but most of it stands for early releases of ver 5.0) and tried what I found: I changed the include of iosream.h to iostream (using namespace std); I switced the 'istream_iterator' lines in the istream file. I even got rid of the anoying warnings.
Still nothing.

Please help.

Tarbush
0
tarbush
Asked:
tarbush
1 Solution
 
danny_pavCommented:
what warnings do you get?  what do you try to do?  What happens?
0
 
tarbushAuthor Commented:
to Danny_pav:
The comment I get is the usual ....4786.
It is removed with the #pragma directive.
0
 
nietodCommented:
I can assure you that these functions ussually do work.  This must be something you are doing wrong.  I would restore the original lines in the header files and try to see what the problem is.  Can you post your code?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
arbitraryCommented:
try applying sp2
it works better with templates and STL

0
 
tarbushAuthor Commented:
to arbitrary:

what is sp2?
thanks
0
 
nietodCommented:
Can you post the relevant code?
0
 
PaullkhaCommented:
sp2 means service pack two. The most current I know of is service pack 3. Many files for C++, VB, and on, will be replaced with this service pack. If you download from the web, a T1 line would be nice since you will need 90megs+. (10megs per cab file)

Post the code, code is key!
0
 
pstgCommented:
You must "wrap" the #includes inside the std namespace, so there are no collision between Microsoft stuff and STL...

0
 
tarbushAuthor Commented:
to pstg:
what do you mean by "wrap"? If you are refering the stdio.h file - I used the <stdio> and not <stdio.h> (This is a documented MSVC++ 5.0 bug).

Please advice
thanks, tarbush
0

Featured Post

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now