Hello to everybody,
I'm not a fan of solutions that just mask issues rather really fix
things. And IMHO this approach only relaxes coders and makes them fall
for other pitfalls. e.g. next code still remains broken:
const char * myData;
{
TQString str = someString();
myData = str.utf8()
}
IMHO the better way would be to make the API stricter. E.g. remove
(hide by macro) operator const char *() for TQCString, It will reveal
most of potentially erroneous uses like described.
Just my 2 cents.
вс, 3 февр. 2019 г. в 14:55, Slávek Banko <slavek.banko@xxxxxxx>:
>
> Hello to all programmers,
>
> please give your attention and share your opinion to the proposed patch
> for TQt3. For a detailed description of the problem, see the
> pull-request:
>
> https://mirror.git.trinitydesktop.org/gitea/TDE/tqt3/pulls/6
>
> Cheers
> --
> Slávek
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
