Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
My foreign.tst testsuite currently contains
(with-foreign-string (fv e b "ABC" :encoding charset:utf-16)
(list e b))
#+UNICODE (4 10) ; #\uFEFF is added upfront
However, it fails in my current builds, because UTF-16 is not available in my current build.
The problem is that the testsuite completely aborts, since a read-error is generated. Remaining tests are not processed!
*** - READ from #<INPUT BUFFERED FILE-STREAM CHARACTER #P"foreign.tst" @159>: #<PACKAGE CHARSET> has no external symbol with name "UTF-16"
Any suggestion about how to test some encodings only when available?
Or should just test.lisp protect itself against read-errors?