Resource Strings vs. CStrings
-
I have some messages that are dispalyed in my application (error messages, welcome messages). I was wodering what is the best way to define those strings: 1. in a resource file, or 2. define my own const CString object in a common header file. I would like to hear your pros and cons on both options. Thanks! Best regards, Alexandru Savescu P.S. Interested in art? Visit this!
-
I have some messages that are dispalyed in my application (error messages, welcome messages). I was wodering what is the best way to define those strings: 1. in a resource file, or 2. define my own const CString object in a common header file. I would like to hear your pros and cons on both options. Thanks! Best regards, Alexandru Savescu P.S. Interested in art? Visit this!
If you ever think of doing something like localisation, resources are the way to go (probably even a resource DLL). But if you are happy with one (or maybe very few, with different binaries) languages, you can probably stay with const strings in your application. Both are Unicode-ready, but when you choose english as your applications language, you will probably not need this. Just my 2 Euro-cents "My opinions may have changed, but not the fact that I am right." Found in the sig of Herbert Kaminski