Can we find a solution to this?
How about this: don't sort byte-by-byte. Sort by the UInt32 numbers.
My concern is some structs, for example,
struct Dummy {
Int8 a :4;
Int8 b :3;
Int8 c :1;
}
Does the endian order affect the bit order in the struct? If so, some of my
bit operation code will have to be rewritten.
Max
--- Michael Glickman <[EMAIL PROTECTED]> wrote:
> > It will be muchg safer to agree to keep creator and type in relation to
> endiannes. In > > this case taking 'myCR' as creator ID, 'm' goes to LSB for
> ARM and to MSB for m68k. This > is how the compiler should treat 'myCR' as
> well. Currently I can't see any problem with > that approach, can you ?
>
> Actually there is a problem: sorting.
>
> Well, this is what happens when a big-endian concept is applied to a
> little-endian machine...
>
> M.
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please
> see http://www.palmos.com/dev/tech/support/forums/
=====
-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-
Got Palm?
Get ExBox at http://www.weirdwww.com/ExBox to beam anything!
__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
