On Mon, 9 Oct 2000 16:50:47 +0200 (MEST), [EMAIL PROTECTED] wrote:
>>> gets pretty hairy and complicated in some places. He is considering just
>incoporating
large
>>> portions of cdrecord and cdda2wav source into his program.
>>>
>>> Would there be any use for a libcdrecord and how much work would it be?
>>IMO it would be useful. It's not so difficult to take some routines from
>>cdrecord's code, I've done some very little experiment and did not face
>>particular difficulties. The only matter is the complete lack of
>>documentation. You'll have to guess the effect of many routines.
>
>I've got this question several times.
>The answer is:
>
>making it possible to have libcdrecord would force me to do massive changes on the
>source code.
>
>- no global vars
That wouldn't be too hard to fix.. unless you have a lot of them. How many globals
are we
talking?
>- All code must be reentrant.
Yes... but most of your code probally already is.. Removal of globals will cover 90%
of this
wouldn't it?
>- People would ask me to support calling of "parts" of the whole thing.
>I don't have the time to do this in a reasonable time-frame... sorry.
Well assume for the sake of dicussion assume that you don't have to do any work.
Since
there is someone who is semi-interested in implementing it.
What I really want to know is would there be sufficent demand and need to make such an
effort?
How much work would you estimate "massive" code changes is?
Looks like one or 2 of the front end people might be interested as well.
Seems to me that a good libcdrecord would make things easier on you as modularization
of the
codebase would promote good structure and allow others to help maintain the codebase.
You
have done more than you fair share.
Perhaps someone could just go whole hog and implement a new structure with a well
though out
interface rather than just a lib conversion.
--
Richard A. Smith Bitworks, Inc.
[EMAIL PROTECTED] 501.846.5777
Sr. Design Engineer http://www.bitworks.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
