Converting from Borland to Visual C++
-
This was posted in the Visual C++ lounge as well... I am converting several applications from a combination of Borland Builder 4/5 and Borland C++ to Visual C++. Does anyone have any advise or source of information that can help us get a better picture on the abuse we are inflicting upon ourself? Thanks!
-
This was posted in the Visual C++ lounge as well... I am converting several applications from a combination of Borland Builder 4/5 and Borland C++ to Visual C++. Does anyone have any advise or source of information that can help us get a better picture on the abuse we are inflicting upon ourself? Thanks!
I once converted a simple 'driver' for an LPT1 interface card I made from borland C to visual C... as far I can remember one of the main troubles I had was unsigned/signed problems
Cheers,
Marc:beer: Click to see my *real* signature :beer:
-
This was posted in the Visual C++ lounge as well... I am converting several applications from a combination of Borland Builder 4/5 and Borland C++ to Visual C++. Does anyone have any advise or source of information that can help us get a better picture on the abuse we are inflicting upon ourself? Thanks!
I replied to your msg there but I forgot to say that I believe it really depends on where your knowledge and expertise in compiler or development suite is. Meaning if you are adept at VC++ and don't know any Borland or adept at Borland but don't know VC++ is harder than knowing both well. I knew Borland C++ 5.01/5.02 and OWL but very little VC++. Most of my problems had to do with the iostream or runtime implementation differences. For example, in BC I inherited code that wrapped all of the old C runtime library stuff for file I/O but in a C++ class. So, behind the scenes fopen(), fclose(), fseek() and all commands that used file handles were called. BC automatically tied the operator overloading of operator << to ostream to this file that was opened via the C runtime library calls. When I went to VC I was surprised that it did not do this and thus had to convert the classes to use iostream C++ runtime library. e.g. use ofstream. There were some gotcha's and other issues. I don't know of any resources that you can preview that can warn you of these things. Your best bet is to get someone knowledgeable in Borland and someone knowledgeable in VC and set them down and discuss line by line what BC is doing and how would you do it in VC. An interpreter of sorts. Good luck.