On Tuesday 17 March 2009 18:36:46 [email protected] wrote: > Mike wrote: > > The oggplay relies on fork() (superficially if you ask me) and does not > > It isn't quite so superficial. The fork is there so that when playing > multiple tracks things don't get clagged up. Was easier doing this than > tracking down all the state destruction and rectifying it. If your use is > single tracks only then there is no need for the fork() call. > > My goal with oggplay was to take essentially the same arguments as mp3play. > i.e. drop in compatible, hence the mess. > > PS, your patch only addresses one of the fork() calls. There is another > harmless one :-)
i'm aware of the ip one (-i), but i honestly dont care about oggplay. i spent 30 seconds of effort to get it working in the common case (`oggplay foo.ogg`). -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
