General complain about LPWSTR in API instead of LPCWSTR...

[omascia]

All over the brand new API, when taking a string as input, it generally is declared LPWSTR (non const), which is a pain in the {you know what } when calling them from C++. Why haven't these API been declared to take CONST strings (that is LPCWSTR for instance) when the intent is not to update them anyway?

[Roman - Tracker Supp]

Hello omascia,
Actually we use const strings wherever possible in our COM API internal definition.
The problem is that we publish our COM API in the form of MS type library (TLB).
It is universal and makes COM API available for most development environment at the expense of losing some information, including const qualifiers.

[omascia]

Hello omascia,
Actually we use const strings wherever possible in our COM API internal definition.
The problem is that we publish our COM API in the form of MS type library (TLB).
It is universal and makes COM API available for most development environment at the expense of losing some information, including const qualifiers.

Thanks. Unfortunately this leveling down forces C++ teams to add const_cast<> or C-style casts in many places, and though it won't shake earth too badly, it feels wrong, in 2016. Maybe that's just me though, so:)

[Roman - Tracker Supp]

I agree with you. We will discuss what can be done without breaking backward compatibility.