Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Currently our code uses a for-loop for filling a buffer holding a Unicode string with some Unicode character value (of type wchar_t). There’s wmemset() function in Visual C++ using which we could replace a loop with a single function call in that code. However we’re concerned about portability – we’d like to leave code as portable as possible and so introducing non-portable or poorly portable stuff is a bad idea.
Will using wmemset() hurt portability and to what extent?
It’s mentioned in the C++ standard
cwchar(Table 48) at least and hence should be pretty standard. So I guess it should not hurt portability