>>>>> "M" == Mark Taylor <[EMAIL PROTECTED]> writes:

    >> Also!  there's been some talk of removing the cmd-line parsing
    >> code from the library.  i think that's a bad idea, at least
    >> until there's some documentation on what you're supposed to set
    >> in that big bit-structure, you have two choices, just feed it
    >> embedded cmd-args, or read the source.  while i'm okay reading
    >> the source, it shouldn't be that hard just to figure which flag
    >> you need to set to get something done.
    >> 
    M> good point!  So Takehiro: consider this another vote for
    M> keeping parse.c in the library.

I don't think parse.c need to be in the library. parse.c in frontend/
directory will be a good sample code to explain the "big bit-structure"

and even if the library does not contain parse.c, you can still use it
with LGPL. 
--- 
Takehiro TOMINAGA // may the source be with you!
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )

Reply via email to