You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should accept an UTF-8 string. It accepts an ANSI text right now and we can't control conversion. Solution: Change all the LPSTR parameters to void* or it's better to update all the functions with the BSTR parameters
The text was updated successfully, but these errors were encountered:
I plan to modify all the public functions that accepts the strings and insert the BSTR->UTF8 converter inside each procedure. In that case we'll need to change all the prototypes to BSTR/LPWSTR.
That IMO would be the most convenient approach. Basicly LPSTR params get the BSTR->ANSI treatment by the compiler and although invisible the string conversion overhead is still there.
Note that some strings are probably in/out params i.e. will need both BSTR->UTF-8 and UTF-8->BSTR on retval.
It should accept an UTF-8 string. It accepts an ANSI text right now and we can't control conversion.
Solution:
Change all the LPSTR parameters to void* or it's better to update all the functions with the BSTR parameters
The text was updated successfully, but these errors were encountered: