[Ecls-list] Automatic string conversion - wanted or needed?

Pascal J. Bourguignon pjb at informatimago.com
Thu May 1 09:44:00 UTC 2014

Matthew Mondor <mm_lists at pulsar-zone.net> writes:

> Possible solutions:
> - Carefully check other possibly affected code in the tree.
>   Perhaps replace the checks like that for bug 290 to explicit
>   coercions to base_string, which may signal a condition as needed if a
>   character cannot be encoded to ASCII.
>   Another possibility would be to encode to UTF-8 instead in the
>   future, although this may cause other problems depending on libc/OS.
>   A configurable, system-specific default FFI encoding could perhaps be
>   used in the future (i.e. using a dynamic variable to define the
>   encoding for FFI/C external encoding)...

clisp distinguishes the following encodings:

CUSTOM:*DEFAULT-FILE-ENCODING*   for :external-format :default
CUSTOM:*MISC-ENCODING*           for the rest
CUSTOM:*PATHNAME-ENCODING*       for pathnames
CUSTOM:*TERMINAL-ENCODING*       for the terminal

__Pascal Bourguignon__
"Le mercure monte ?  C'est le moment d'acheter !"

More information about the ecl-devel mailing list