This blog is about developing Windows applications using Visual Studio. All postings on this weblog are provided "AS IS" with no warranties, and confer no rights. Use of any samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
Your host Nikola Dudar is a Program Manager in Windows division of Microsoft Corporation. He has been working on Windows Web Services API during Windows 7 and various additions to Visual C++ during VS2005 and VS2008. More details are in LinkedIn profile under Nikola's formal name Mykola Dudar.
If you are interested in program management and project management, check out my other blog at http://www.pmsnack.com/ where I collect best practices and other topics interesting to program and project managers.
To send feedback, comments or requests for new posts, please use the contact form.
I am trying to understand number of customers use this #define and user scenarios it is currently used in. If you see #define _HAS_EXCEPTIONS in your source code, could you please reply to me directly or just comment here info on
- what kind application is this?
- what are reasons to use this #define?
- how big is an impact on you if this #define was removed from STL inVS2005?
Please specify in your reply if you want me to post your comment online. Yes is assumed by default.Thanks,Nikola
I wish I'd found this earlier... Using the STL without exceptions is crucial to us in our code shop. We write games and when we discovered it was just a beta feature we ended up having to rewrite all our containers.
Umm, could have been easier to switch to STLPort