unicode - Support for C-Functions in Future Version of C++ / CString vs. LPCTSTR / Binary Datatypes -


we have migrate mfc-project (multibyte code/ansi) unicode/windows 7. in project many c-functions _tcschr, _tcsncpy, _stprintf, _tcslen... used.

lpctstr used instead of cstring. char* used make binary operations.

i think there many pitfalls lpctstr , unicode(example: _tcslen).so want replace lpctstr cstring/ const cstring. new function should use string-methods of cstring.

char should replaced tchar, because cstring based on tchar. don't care char , binary operations in future. length of 8 bit seems stall 8 bit, encodings, ..?  

so questions are:

  • how long planned support old c-funktions in future (vs 2013, vs 2015,...)?
  • is there tested library based on cstring replace old c-functions (less effort)?
  • what datatype should use binary operations future support?
  • is there reason not replace lpctstr through cstring (with cast operator lpctstr)?


Comments

Popular posts from this blog

qt - Using float or double for own QML classes -

Create Outlook appointment via C# .Net -

ios - Swift Array Resetting Itself -