On Tue, Jun 18, 2013 at 9:47 PM, Bruce Perens <[email protected]> wrote:
> On 6/17/2013 2:20 PM, David Rowe wrote:
> > Not sure if this warrants an extra library. What do others on the list
> think?
> I would like to see each modem presenting the same API, and in its own
> DLL. Then, an application could choose its modem at run-time with
> dlopen(), without wasting any memory on a modem it isn't going to use.
>
Sound like you're thinking that this should really be a collection of
libraries? So in this case, regardless of the project name "rfmodem" or
otherwise, the library in this case would be libgolay23?
> > + the golay codes implements forward error correction (FEC). Its a
> different layer from the modem. So the name "rfmodem" is not suitable.
> I think we can find some name for accessory routines that go with modems
> but are not bound to a specific modem. It doesn't matter tremendously if
> it's "rfmodem" or "libdavid". I guess that FEC has use in telephony
> modems and magnetic recording, too, but I doubt we're going to confuse
> anyone whatever we name it.
>
> Just let me know. I don't really have enough knowledge in this area to
make an informed suggestion but changing it would only take about 30
seconds at this point since nothing is actually building against it yet...
Richard
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
