[vorbis-dev] alloca() problem with CodeWarrior

[Michael Smith]

>The ov_alloca() implementation could be done fairly trivially using a fixed 
>memory pool with trivial block compaction and merge.  It wouldn't have to 
>be that robust since you know exactly how/when it's called.  The only 
>really important thing is to make sure that it's reentrant and thread safe 
>somehow (actually, come to think of, how is ov about thread safety?)

Without wanting to get into the rest of this...

All the vorbis libraries are fully reentrant - there are no _known_ bugs
here. Multiple encoder/decoder instances in seperate threads are fine.
Using a single encoder or decoder across multiple threads requires 
external synchronisation to be safe (this isn't provided by the core libs
because relatively few people need or want it, and portable threading is
rather difficult)

Michael

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.