Pascal J. Bourguignon

Confusing error message: "*PATHNAME_ENCODING* on this platform can only be ~S"

Accepted and rejected key arguments for defgeneric/defmethod. (7.6.4)

On 17 Nov 2017, at 21:26, Bruno Haible haible@users.sf.net wrote: The important points are: People want regular expressions that work, i.e. are correct with non-ASCII character and are not terribly slow. 98% of the users on Unix are in UTF-8 locales nowadays. The available options are not only (citing Sam) 1. drop regexp 2. fix regexp to use wide chars 3. use pcre (which probably does not suffer from this problem) 4. ignore the issue because it works on ASCII and that all that matters. ;-) but also...

On 17 Nov 2017, at 16:40, Sam Steingold sds@users.sf.net wrote: All character-by-character processing in clisp is slow yep, that was first reaction too. so, our options are: drop regexp fix regexp to use wide chars use pcre (which probably does not suffer from this problem) ignore the issue because it works on ASCII and that all that matters. ;-) or: • signal an error only when misc-encoding is not 1-1. [bugs:#691] https://sourceforge.net/p/clisp/bugs/691/ regexp:regexp-split uses wrong offsets when...

On 17 Nov 2017, at 19:52, Sam Steingold sds@users.sf.net wrote: does regexp handle multibyte chars correctly? iow, even if we do in regexp what we already do in pcre, we still need to make sure that the underlying regexp library DRTR. On Darwin 17.2.0, there is an API for wide characters: int regwcomp(regex_t *restrict preg, const wchar_t *restrict widepat, int cflags); int regwexec(const regex_t *restrict preg, const wchar_t *restrict widestr, size_t nmatch, regmatch_t pmatch[restrict], int eflags);...

On 17 Nov 2017, at 13:24, Jörg Höhle hoehle@users.sf.net wrote: Citizen X buys a cheap house near an airport. It's cheap, because nobody wants to live & sleep near an airport. Then he complaints about the noise at night. In some cases, the jurisdiction is such that indeed, the airport is condemned to restrict flights at night. Here, instead of implementing a regexp in Lisp (e.g. cl-pcre) which would not suffer from that bug, a poorly advised idea was to interface to an external C library, which from...

regexp:regexp-split uses wrong offsets when *misc-encoding* is not 1-1.

Oos, sorry, current clisp from mercurial doesn't compile "out of the box" on macOS...