🚀 go-pugleaf

In article <7nsj0za.thinman@netcom.com>, thinman@netcom.com (Lance Norskog) writes:
|   The book says (on Pg. 8-40)
|   <WAVE-form>  ->  RIFF(  'WAVE'			//Form type
|   			<fmt-ck>		// Waveform format
|   			<data-ck> )		// Waveform data
|   <fmt-ck>  -> 	fmt(	<wave-format>		// WaveFormat Structure
|   			<format-specific>	// Dependent on format category

| Guess: Parenthesis in the above grammar means "new block",
| which gets its own 4-byte length field.

| Look at the rest of the file and count out the bytes.
| I'm sure you'll find that they agree with the two section
| length fields at the beginning.
| 
| This seems to be compatible with Electronic Arts' IFF format.

This is correct, RIFF was modelled after the IFF format.  The blocks are
called "chunks".  Any software reading the WAVE format should (to remain
upward compatible with future iterations) skip chunk ID's that it
doesn't recognize, made easy by having the length of the chunk following
the tag.  Don't just assume that chunks will appear only in the specified
sequence.

-Russell Williams