> In case you´re interested... I´ve written up my idea on how an (expandable) > shared library should look like. The URL is http://www.smcc.demon.nl/ccvt/ > This is a draft, not fully completed yet, and open for debate. It contains > documentation from both the programmers point of view (us!), and the > library maintainers/writers (ehm, us? :)) POV. Would it be a performance win in some cases to be able to x=f->open(h,w) // CVT_SIZE_UNKNOWN for unknown x->function(...) .. f->close(x) So that the library can build optimised tables or hand back functions optimised for known sizes (CIF, QCIF, multiple of 16 pixel wide etc) ?
