ogg dev - Feb 2008 - Ogg bitwise.c bit tracking

It's very small, maybe it could be made a separate statically linked lib ?
Or some of it inlined.

That said, libogg is small too, and some of the routines in there are quite
small as well.

Yes, all that is reasonable. The original argument was that we need a
library anyway, no one noticed the function call overhead, and using
libogg simplified the embedding.

Now, we'd like to remove libogg entirely as a dependency to avoid
confusion when using other containers, but that's an api change...

 -r

On 09/02/2008, Ralph Giles <giles@xiph.org> wrote:
> Yes, all that is reasonable. The original argument was that we need a
> library anyway, no one noticed the function call overhead, and using
> libogg simplified the embedding.
>
> Now, we'd like to remove libogg entirely as a dependency to avoid
> confusion when using other containers, but that's an api change...
As far as libvorbis is concerned, wouldn't the step of copying the
bitpacker into libvorbis, where the functions are only used
internally, just allow a dependency change?

There is of course the bit of the libvorbis API which talks in terms
of ogg_packet structures, but maybe we could replicate the definition
of that in a vorbis header file (inside of #ifndef _OGG_H).

Removing the bitpackers from libogg would of course be an API change
to libogg, but we could defer that.

K.