| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 09 Feb 2007 18:10:20 +0300 From: Sergei Organov <osv@...ad.com> To: Jan Engelhardt <jengelh@...ux01.gwdg.de> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: somebody dropped a (warning) bomb Jan Engelhardt <jengelh@...ux01.gwdg.de> writes: > On Feb 8 2007 08:33, Linus Torvalds wrote: >> [...] > What C needs is a distinction between char and int8_t, rendering "char" > an unsigned at all times basically and making "unsigned char" and > "signed char" illegal types in turn. AFAIK, C already has 3 *distinct* types, "char", "signed char", and "unsigned char". So your int8_t reads "signed char" in C, uint8_t reads "unsigned char" in C, while "char" is yet another type that is not compatible with those two. Yes, the names for these types are somewhat confusing, but that's due to historical reasons, I think. Overall, signed char == tiny signed int == tiny int unsigned char == tiny unsigned int char != signed char char != unsigned char where tiny == short short ;) Rules of thumb: don't use bare char to store integers; don't use signed/unsigned char to store characters. [strxxx() routines take char* arguments as they work on '\0'-terminated character arrays (strings). Using them on arrays of tiny integers is unsafe no matter how char behaves on given platform (like signed or like unsigned type).] -- Sergei. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists