Mike Broderick
asked on
I need the definition of "fillorder" (MSB2LSB, etc.)
I am working with libtiff, and fill order keeps coming up. Could somebody please tell me exactly what fill order is?
I may be dense, but I cannot determine exactly what fill order is. My knoledge of CPU architeture is not bad, but I remember words get loaded into registers or memory, not filled. 32 gates open up on a bus and all values are transferred at once during a clock pulse.
I may be dense, but I cannot determine exactly what fill order is. My knoledge of CPU architeture is not bad, but I remember words get loaded into registers or memory, not filled. 32 gates open up on a bus and all values are transferred at once during a clock pulse.
ASKER
Are there C statements that work differently if the bit order is MSB or LSB? For example the a >> b statement?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I thought about something extra here, since I didn't get that explanation correct. If you are only using one operating system, or one application type, then bit order is not so important, because it will always be interpreted a certain way.
An analogy would be reading order between the U.S. and Japan. It is not so important what the order of bits, but how you read them, and interpret them. If bits are written in a certain order, then they need to be read in that same order.
An analogy would be reading order between the U.S. and Japan. It is not so important what the order of bits, but how you read them, and interpret them. If bits are written in a certain order, then they need to be read in that same order.
I believe you are referring to is the bit order within the image (MSB or LSB).