Visual studio is rather silly.

In one project, just changing the character set to unicode was enough for the program to work.

In another project, exact same code, I also needed to add a command-line argument to enable unicode.

Isn't. That. Just. Silly.

  • 1
    Makes you wonder why it isn't the default
  • 0
    @SortOfTested yup.
    onlyvone thing to say here:
  • 0
    @SortOfTested Because before UTF Windows made their own support for extended characters table, and a lot of legacy software relies on that. Even though changing the default encoding wouldn't be much work, it would break a lot of old software businesses rely on. That's a huge problem, as authors (and often the source code as well) are lost.
  • 0
    Twas sarcasm; we all know the answer is "because windows" 😋. That said, it should still be the default for new projects in 2020.
Add Comment