The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Well that is a different issue; I was talking about the answers posted to questions in some of the Microsoft forums. I have always found (with a few exceptions that are less important) the information on MSDN to be useful and well presented.
But when I built the program all the version related functions gave LNK2019 errors, unresolved external symbol.
Go back and #define WINVER and _WIN32_WINNT and recompile. The old version.lib is for legacy desktop applications. It sounds like you are either using an older compiler or targeting an older operating system < Windows 8.
It's basically a documentation issue. The documentation is incorrect if you are targeting older platforms. Much of the documentation will be moving to GitHub.
No, none of those, it's a linker problem, not compiler. The issue has nothing to do with versions of Visual Studio or Windows (I'm using VS2017 on Windows 10), it's purely the fact that the A versions of those functions are not in Mincore.lib, despite the statement in the documentation.
But this issue is purely about the C/C+ Windows libraries. And there are still many programs around that use ASCII. And judging by questions here, many new programmers are not being taught to use Unicode.
But seriously. I am not defending either stance, merely saying what is the reality. Bjorn had the chance when he created C++ to make Unicode the default, but since he didn't it is still a PITA to do it.
Bjorn had the chance when he created C++ to make Unicode the default, but since he didn't it is still a PITA to do it.
I haven't done C++ in a dozen years (never looked back after C#), and I remember that the Windows SDK had a pretty decent set of macros that invoked either the A or W variants of pretty much all APIs based on compiler flags. Once I had settled into a routine of writing all my code "following that style", it was pretty much a no-brainer.
Or so I recall. OTOH it's not like I have any reason to be trying to paint a prettier picture of C++ than what it was actually like for me.
Agreed...took me a while to get used to it, but once you've settled into the pattern, it became second nature to me. But making the transition was painful.
My surprise was that this isn't what newcomers are getting exposed to from the get-go in this day and age, so they don't have to "unlearn everything they thought they already knew about string manipulation".
Hilarious! Loved Jamie Olivers christmas turkey as well!
Anything that is unrelated to elephants is irrelephant Anonymous - The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 - Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain