>> 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...

Still, there's one guy or gal whose job description is to be in charge 
of it, just in case.  Now, said guy or gal, may be responsible for 
hundreds of these single-function libraries, but there still needs to be 
someone to wake up at 2am when a someone figures out how to read the 
encryption key in memory, or that you thought would be secure since you 
ROT-13ed it.  Twice.

>
> Now, code to drive custom hardware implementations? That might be more
> tricky.

There you go.

-- 
/*Francois Labreque*/#local a=x+y;#local b=x+a;#local c=a+b;#macro P(F//
/*    flabreque    */L)polygon{5,F,F+z,L+z,L,F pigment{rgb 9}}#end union
/*        @        */{P(0,a)P(a,b)P(b,c)P(2*a,2*b)P(2*b,b+c)P(b+c,<2,3>)
/*   gmail.com     */}camera{orthographic location<6,1.25,-6>look_at a }

Post a reply to this message