libera/#commonlisp - IRC Chatlog
Search
15:19:23
Nilby
Unfortunately what people think of as a character isn't really the unicode code point which is likely your CL character, but rather graphemes as delivered by say sb-unicode:graphemes.
15:20:57
splittist
Many of the popular lisp compilers provide a way to associate characters with Unicode code points, and therefore ways for library authors to associate the information provided by Unicode data tables, and perform Unicode algorithms, on characters. But as Nilby says, anything one instinctively thinks about characters is probably wrong for some set of situations.
15:23:22
jackdaniel
if I had an euro for each time I had a bad thought about unicode, then I could buy a coffee
15:23:37
Nilby
even disregarding input and output, code point comparison is troublesome without normalization
15:25:20
jackdaniel
I would not be surprised if someone had proven that one of uax implies turing-completness of the unicode
15:35:05
NotThatRPG
On SBCL, when we use CFFI to link new C code, do we need to use the same C compiler that was used to build SBCL? Asking because SBCL is built with default (Apple) cc on my laptop, but I *think* I need to use the brew gcc to link in libuv (which comes from brew). Do I need to rebuild SBCL with brew's gcc for that?
15:42:40
yitzi
NotThatRPG: cffi is generally not linking to sbcl. It is loading shared libraries and calling functions in them. Along with marshalling, etc
15:50:02
NotThatRPG
My problem is that CFFI-grovel isn't finding the right includes or libraries and there doesn't seem to be anything I can do to fix that.
15:50:19
NotThatRPG
It's configuring itself and there are not obvious hooks to override that configuration.
15:51:33
NotThatRPG
I was hoping that using a different value for `cffi-toolchain:*cc*` would help (because the other gcc knows the right include and lib directories) but I seem unable to change the value of `*cc*` in a way that sticks, or set flag variables.
15:55:55
NotThatRPG
_death: OK, but that requires me to break the abstraction of the `cl-async` library, which seems wrong. Shouldn't the configuration of the local C compiler be kept out of the grovel file?
15:56:44
NotThatRPG
It seems like a mistake that the person who writes the grovel file has to know everything about where header and library files are stored on all possible platforms.
15:58:36
yitzi
NotThatRPG: CFFI has some issues with respecting CFLAGS that are unresolved. https://github.com/cffi/cffi/pull/146
16:00:06
NotThatRPG
Seems like somehow CFFI-Grovel (or the ASDF interface thereto) is resetting a lot of the cffi-toolchain config, too.
19:36:56
nij-
jackdaniel What's the backend of petalisp? Is it powered by lower-level libs like blas or lapack, or anything similar?
21:19:21
NotThatRPG
petalisp looks really cool, but the license is problematic. It would be nice if we could build images using it that are not also licensed under AGPL, but that seems impossible. I like the idea of making it available in a copy-left way, but the idea that any code calling petalisp must also be copyleft is more restrictive than I can live with :-(