sharplispers / cl-jpeg-tests Goto Github PK

That includes clisp32, allegro, cmucl, sbcl32, ccl32 and ecl in Travis CI runs.

The problem is due to different fixnum precision and hence different rounding error in fixed point maths.

Title says it all, as does the comment in decode-stream. It would be nice to support reading progressive images.

We should make sure that we're testing functionality that is available via exported interfaces. If we're using internal symbols here, that suggests these symbols should be exported. I suppose this is really a cl-jpeg issue, but it seems easier to track it here.

Also, I suppose unit tests for non-exported functionality might be useful too, but that we should separate that stuff out somehow.