On Thu, Aug 25, 2022 at 02:07:12AM +0100, Jessica Clarke wrote: > On 25 Aug 2022, at 01:29, Konstantin Belousov <[email protected]> wrote: > > + const unsigned char *u1 = __DECONST(const unsigned char *, s1); > > + const unsigned char *u2 = __DECONST(const unsigned char *, s2); > > Why is __DECONST needed? Casting from const char * to const unsigned > char * should never warn, surely?
I requested the use of __DECONST there. Nobody knows what would be next trend in the C language breaking among compiler writers. We guarantee that __DECONST() is adopted to whatever warnings are added.
