freenode/lisp - IRC Chatlog
Search
5:45:33
fiddlerwoaroof
Bike, I'm confusing two things, it's interesting that #{} and #[] aredescribed this way: "The combinations marked by an asterisk (*) are explicitly reserved to the user"
5:46:32
fiddlerwoaroof
While [] and {} are defined this way: "The characters marked with an asterisk (*) are initially constituents, but they are not used in any standard Common Lisp notations. These characters are explicitly reserved to the programmer."
5:47:47
fiddlerwoaroof
It seems to me that there's an attempt here to distinguish characters that end-users might define reader macros on from characters that non-end-user programmers might define reader macros on
5:48:19
fiddlerwoaroof
Of course, in retrospect, it seems to me that NAMED-READTABLES is the right solution to this sort of problems
14:29:27
opfez
does anyone have experience with cl-sdl2 on raspberry pi? can't get it to compile because it fails trying to run c2ffi
14:30:53
phoe
check the inferior-lisp buffer and/or the REPL, it should contain either the c2ffi invocations or c2ffi error messages
14:31:24
phoe
in the earlier case, you'll have a shell command that you will be able to repeat yourself in a terminal, and you'll get the error messages
14:34:08
opfez
yep, tried running that. the 8.0.1 part is wrong which i replaced with my actual clang version, still didn't work
14:39:58
phoe
weird, I can see that the C-INCLUDE form is supposed to include stdint.h which has these C type definitions.
14:53:20
opfez
in addition to this, i manually went into the sdl2 include file and added a #include <stdint.h>, didn't work either