Am Montag, 12. Januar 2004 20:31 schrieb [EMAIL PROTECTED]:
> | Let me tell you - I have programmed for twenty years without
> | knowing the meaning of little-endian and big-endian. Yes,
> | they had something to do with the order of bytes in an integer,
> | but there are many strange architectures and mixed versions,
> | and there is no need at all to know such things.
> | Yes, knowing such things is directly harmful.
>
> I can only see this if you don't do hardware interface programming
> or if you do but it's all on one $ARCH.
> There are places (like USB host controller drivers) that using
> endian swapping is necessary.
>
> As indeed was necessary here. And the code that was there did the
> job fine. And did not need the concept of endianness or swapping.
> It just did what was to be done.
It did need the concept. It didn't acknowledge that it did so.
That is wrong. That data is in a certain endianness should never be
hidden. We indicate it by using the appropriate macros.
Regards
Oliver
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
