[ogg-dev] eos on continued page
jean-marc.valin at usherbrooke.ca
Mon Feb 25 21:48:43 PST 2008
>> There general idea with Ogg has been to distinguish non-fatal from
>> fatal errors. libogg reports these by returning -1 while still
>> returning the next valid bit of data.
> ok, would non-fatal translate into a SHOULD recommendation in the
> spec, and fatal translate into a MUST?
I assume there there are cases where a MUST isn't respected, yet libogg
is still able to recover something. If it's just a SHOULD that isn't
respected, it shouldn't be considered as an error in the first place.
More information about the ogg-dev