- From: <bugzilla@jessica.w3.org>
- Date: Thu, 05 Apr 2012 00:02:06 +0000
- To: public-script-coord@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16604
John Thomas <therandshow@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |therandshow@gmail.com
--- Comment #7 from John Thomas <therandshow@gmail.com> 2012-04-05 00:02:03 UTC ---
Nice context for byte vs octet -
http://www.tcpipguide.com/free/t_BinaryInformationandRepresentationBitsBytesNibbles-3.htm
Careful with "short int" and "unsigned short int" as octet I believe generally
(though w/ basic data type lengths you can never be sure) maps to C/C++
signed/unsigned char != signed/unsigned int
http://www.cplusplus.com/doc/tutorial/variables/
Ultimately, even though you might confuse byte with short with octet, you will
rarely confuse octet with something that is not 8-bits long.
Also, with octet - it's not about range, it's about storage size, although if
an octet's unsigned (which I think it has to be), it should go from 0-255
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 5 April 2012 00:02:08 UTC