|
![](/i/fill.gif) |
> As for proprietary libraries, you do realise that they need maintaining,
> being ported to new platforms, etc...
Large, complex applications need maintaining. A small single-function
library that already works correctly? Why would it need any maintenance?
As for porting, most of this stuff seems to be written in ANSI C, and
it's pure algorithmic code. You would /think/ it's fairly portable...
Now, code to drive custom hardware implementations? That might be more
tricky.
Post a reply to this message
|
![](/i/fill.gif) |