Re: LIST-TABLES problem on LispWorks

I get a failed test from UFFI:

CL-USER 1 > (asdf:oos 'asdf:test-op :uffi)
Doing 64 pending tests of 64 tests total.
 :STRTOL.1 :STRTOL.2 :STRTOL.3 :STRTOL.4 :ATOI.1 :ATOI.2 :ATOF.3
:GETENV.1 :GETENV.2
 :GETHOSTNAME.1 :GETHOSTNAME.2 :GETHOSTNAME.3 :GETHOSTNAME.4
:GETHOSTNAME.5 :UNION.1
 :UNION.2 :UNION.3 :UNIONS.4 :UNIONS.5 :ARRAY.1 :ARRAY.2 :STRUCTS.1
:STRUCTS.2 :CHPTR.1
 :CHPTR.2 :CHPTR.3 :CHPTR.4
Test :CHPTR.5 failed
Form: (LET ((UFFI-TESTS::FS (UFFI:ALLOCATE-FOREIGN-OBJECT
:UNSIGNED-CHAR 128))) (SETF (UFFI:DEREF-ARRAY UFFI-TESTS::FS (QUOTE
(:ARRAY :UNSIGNED-CHAR)) 0) (UFFI:ENSURE-CHAR-STORABLE #\a)) (SETF
(UFFI:DEREF-ARRAY UFFI-TESTS::FS (QUOTE (:ARRAY :UNSIGNED-CHAR)) 1)
(UFFI:ENSURE-CHAR-STORABLE (CODE-CHAR 0)))
(UFFI:CONVERT-FROM-FOREIGN-STRING UFFI-TESTS::FS))
Expected value: "a"
Actual value: "A
ò·X£ò·§".
 :TIME.1 :TIME.2 :TIMEOFDAY.1 :TIME.3 :C-TEST.1 :C-TEST.2 :C-TEST.3
:C-TEST.4 :C-TEST.5
 :C-TEST.6 :C-TEST.7 :C-TEST.8 :COMPRESS.1 :COMPRESS.2 :COMPRESS.3 :UNCOMPRESS.1
 :UNCOMPRESS.2 :UNCOMPRESS.3 :CAST.1 :CAST.2 :FVAR.1 :FVAR.2 :FVAR.3
:FVAR.4 :FVAR.5
 :FVAR.6 :FVAR.7 :FVAR.8 :FVARST.1 :FVARST.2 :FVARST.3 :FVARST.4 :FVARST.5
 UFFI-TESTS::FVARST.6 UFFI-TESTS::FVARST.7 UFFI-TESTS::FVARST.8
1 out of 64 total tests failed: :CHPTR.5.
Error: test-op failed
  1 (continue) Retry performing #<ASDF:TEST-OP (:FORCE T) 200DBCE3> on
               #<ASDF:SYSTEM "uffi-tests" 220AE0E3>.
  2 Continue, treating #<ASDF:TEST-OP (:FORCE T) 200DBCE3> on
    #<ASDF:SYSTEM "uffi-tests" 220AE0E3> as having been successful.
  3 Retry performing #<ASDF:TEST-OP NIL 21791A03> on #<ASDF:SYSTEM
"uffi" 22089BC7>.
  4 Continue, treating #<ASDF:TEST-OP NIL 21791A03> on #<ASDF:SYSTEM
"uffi" 22089BC7>
    as having been successful.
  5 (abort) Return to level 0.
  6 Return to top loop level 0.

Type :b for backtrace, :c <option number> to proceed,  or :? for other options

CL-USER 2 : 1 >

On 8/13/06, Kevin Rosenberg <kevin@...> wrote:
> Bill Atkins wrote:
> > Something to do with string encodings maybe?
>
> Something like that, or the LW 5.0 FFI string conversions, rather
> meta-data, I think you are right. OTOH, I think they're are still
> likely issues with postgres 8.x changes in metadata for which CLSQL
> has still not been ported.
>
> I don't have LW 5, but on quick test on the FFI would be to run UFFI's
> test suite. It passes all tests on LW 4.4. If it does the same on LW
> 5, then yes, non-8 bit strings could well cause a problem.
>
> UFFI and CLSQL have some very patchy support for non-ASCII
> strings. But, there is no formal support for non-ASCII strings for
> various wide to narrow and their inverse string conversions.
>
> Kevin
>

--

-- 
Bill Atkins