Follow cl-ffi d130839: arguments of the wrong kind are type-errors
The API reference, Errors and Strings say that cl-ffi's functions declaim
the full domain of their arguments, so that an encoding cl-ffi does not
know, given as :encoding, or a keyword given as a struct type, is a
type-error from SBCL's check, whose message Strings quotes.
Follow cl-ffi b363d27: ffi-error and decoding-error are functions too
The API reference lists the two functions that signal cl-ffi's
conditions, now that the helpers behind them lost their % prefix and took
the conditions' names. The example binding of zlib's compress in Getting
Started takes a plain name, after the workspace's rule for names.
Follow cl-ffi 574f378: string encodings and foreign-type-lisp-type
Strings, Types and Functions and Callbacks describe (:string :encoding
encoding), the string type in another encoding than UTF-8, with an
example for the wide strings of Windows, and say that nil is no string
argument. Types, Functions and Callbacks and the API reference add
foreign-type-lisp-type, the Lisp types defcfun declaims. Libraries and
Saved Images says that a load error is signalled once cl-ffi's lock is
let go, so a handler may load another library.
Home, getting started, a page for cffi's users, types, memory, functions
and callbacks, strings, libraries and saved images, errors, the API
reference, and platforms and testing, with a sidebar.
