Discussion:
just upgraded from MSVS 2005 to MSVS 2012
(too old to reply)
Lynn McGuire
2015-11-16 22:12:26 UTC
Permalink
Raw Message
I just upgraded us from MSVS 2005 to MSVS 2012. The worst problem that I had was that we wrote our primary C++ code back in the dark
ages before std:: for the STL. So, we were using "using namespace std;". When I started compiling in MSVS 2012, I had a conflict
between our tuple methods and the std::tuple method. So, I bit the bullet and put std:: in all of our STL objects.

BTW, I also looked at MSVS 2013 and ran into the fact that it only supports UNICODE and has dropped support for ASCII. Since our
product started at Window 1.0, we never has made UNICODE a priority. Looks like we will need to do that some day. I suspect that we
will move to UTF-8, not UTF-16 as we cannot afford the double byte space for each character.
https://en.wikipedia.org/wiki/UTF-8

Thanks,
Lynn
Barry Schwarz
2015-11-16 23:45:15 UTC
Permalink
Raw Message
Post by Lynn McGuire
I just upgraded us from MSVS 2005 to MSVS 2012. The worst problem that I had was that we wrote our primary C++ code back in the dark
ages before std:: for the STL. So, we were using "using namespace std;". When I started compiling in MSVS 2012, I had a conflict
between our tuple methods and the std::tuple method. So, I bit the bullet and put std:: in all of our STL objects.
BTW, I also looked at MSVS 2013 and ran into the fact that it only supports UNICODE and has dropped support for ASCII. Since our
product started at Window 1.0, we never has made UNICODE a priority. Looks like we will need to do that some day. I suspect that we
will move to UTF-8, not UTF-16 as we cannot afford the double byte space for each character.
https://en.wikipedia.org/wiki/UTF-8
While VS2013 defaults to UNICODE, it supports ASCII once you #undef
both UNICODE and _UNICODE. You can do this either in a header by
updating the project properties.
--
Remove del for email
Lynn McGuire
2015-11-18 20:31:31 UTC
Permalink
Raw Message
Post by Barry Schwarz
Post by Lynn McGuire
I just upgraded us from MSVS 2005 to MSVS 2012. The worst problem that I had was that we wrote our primary C++ code back in the dark
ages before std:: for the STL. So, we were using "using namespace std;". When I started compiling in MSVS 2012, I had a conflict
between our tuple methods and the std::tuple method. So, I bit the bullet and put std:: in all of our STL objects.
BTW, I also looked at MSVS 2013 and ran into the fact that it only supports UNICODE and has dropped support for ASCII. Since our
product started at Window 1.0, we never has made UNICODE a priority. Looks like we will need to do that some day. I suspect that we
will move to UTF-8, not UTF-16 as we cannot afford the double byte space for each character.
https://en.wikipedia.org/wiki/UTF-8
While VS2013 defaults to UNICODE, it supports ASCII once you #undef
both UNICODE and _UNICODE. You can do this either in a header by
updating the project properties.
We will probably bite the bullet since we have so many international customers.

Lynn

Loading...