Thread: Unicode
View Single Post
Old 17th November 2009, 14:10   #336
Anders's Avatar
Join Date: Jun 2002
Location: ${NSISDIR}
Posts: 4,941
Windows programmers don't think about that, I'm so used to just calling lstr*, I don't think about the char type. Whats wrong by defaulting to the W versions and only falling back if W does not exists or a option to disable it was set?

Do you have a single example of a function that needs to be called without W when running as unicode (meaning foo should be called with WCHAR* even if fooW exists)?

IntOp $PostCount $PostCount + 1
Anders is offline   Reply With Quote