On Feb 8, 2008 10:44 AM, Timothy B. Terriberry <<a href="mailto:tterribe@email.unc.edu">tterribe@email.unc.edu</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
None of that means there aren't other very good reasons we should pull<br>the bitpacker out of libogg that have nothing to do with speed. People<br>seem to have a philosophical problem with linking to libogg when they<br>
want to mux Vorbis in non-Ogg containers, even though the only<br>Ogg-specific parts of libogg are a single C file which compiles to a<br>single object file smaller than 30K. The only people who actually care<br>about something so small are embedded developers, who would use Tremor<br>
(with its own built-in bitpacker) anyway.<br></blockquote><div><br>It's also a psychological and a "good sw design" issue. You just don't need to have code in your executable that you will never call.<br>
<br>Silvia. <br></div></div>