Am Donnerstag, 8. Februar 2007 16:41 schrieb Sergei Organov:
> > If you do that, le16 is just as valid, especially if declared
> > unaligned.
>
> I don't think so:
>
> 1. 'unsigned char', be it used in the form of 'u8' or not, has neither
> alignment nor endianness problems, while le16 has both.
By simply ignoring the issue.
> 2. The only truth that le16 actually tells to the compiler is that this
> field is 2 bytes in size, and u8[2] tells that either. However, the
No, that tells the compiler it's two fields of 1 byte each.
> u8[2] definition makes it hard to use this field as bare integer by
> mistake, so IMHO it wins from the POV of type-safety as well.
It is an integer. le16 was introduced to avoid u16.
Regards
Oliver
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
