Re: RIFF subchunks

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

On Jul 9, 9:44 pm, Brick Wall <BrickW...@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:
Oh, when I say "all of the docs," I mean the docs containing the level of
detail that I'm interested in. The VB docs are more frequently written with
the assumption that programmers won't need the details.

From my 2003 MSDN CD ..

"little-endian
Refers to a processor memory architecture in which the byte layout is
as follows:
Byte N is the least significant (and, in conventional layout diagrams,
the "rightmost") byte of:
A word composed of bytes N and (N + 1).
A doubleword composed of bytes N, (N + 1), (N + 2), and (N + 3).
A K-byte memory entity composed of bytes N, (N + 1),...,(N + K - 1).
The address of the preceding word, doubleword, or K-byte entity is its
least significant byte, N.

Intel microprocessors always support little-endian addressing. Some
RISC microprocessors can be configured for either big-endian or little-
endian addressing. For a little-endian configuration, the least
significant bit of a 16-bit short value is the "rightmost" bit at byte
N, while the most significant bit is the "leftmost" bit of byte (N +
1).

See also big-endian"

and

"big-endian
A processor memory architecture in which byte N is the most
significant, and in conventional layout diagrams, is the leftmost byte
of:
A word composed of bytes N and (N + 1).
A doubleword composed of bytes N, (N + 1), (N + 2), and (N + 3).
A K-byte memory entity composed of bytes N, (N + 1),...,(N + K - 1).
The address of the preceding word, doubleword, or K-byte entity is its
most significant byte, N.

Some RISC processors can be configured for either big-endian or little-
endian byte addressing. For a big-endian configuration, the most
significant bit of a 16-bit short value is the leftmost bit at byte N,
while the least significant bit is the rightmost bit of byte (N + 1).

The terms "big-endian" and "little-endian" are derived from Jonathan
Swift's Gulliver's Travels.

See also little-endian."

But of course that may not be in there now because "everyone knows
_that_" <g>.

As a Delphi programmer (whoops I said the word <g>), the best money I
_ever_ spent was on a year's subscription to MSDN Library CDs. About
£150 or so now. I believe it includes much lower lever VB stuff too.

Alan Lloyd

.

Relevant Pages

  • Re: RIFF subchunks
    ... my subscription is getting pretty old now. ... Intel microprocessors always support little-endian addressing. ... RISC microprocessors can be configured for either big-endian or little- ... For a little-endian configuration, the least ...
    (microsoft.public.win32.programmer.mmedia)
  • Re: A very quick, informal survey
    ... > order or sequence of data transmission is important. ... First of all your programmers are correct. ... The problem is that what Big-endian means ... If you do everything in Little-endian, then you should just say "its ...
    (comp.programming)
  • minixfs bitmaps and associated lossage
    ... to array of big-endian 32bit gives different results. ... For little-endian we get the same thing, ... but I'm not sure if minix even existed on sparc at that point. ... Everything else is using layouts that never would be recognized ...
    (Linux-Kernel)
  • Re: A question for the group...
    ... And speaking of Big-Endian vs. Little-Endian: ... I was able to get the 32-bit-only Squeak Smalltalk ... Any computable function can be performed ...
    (soc.genealogy.computing)
  • Re: RfD: Signed and Unsigned Word Fetch and Store
    ... host is big-endian, target is big-endian ... host is big-endian, target is little-endian ...
    (comp.lang.forth)