libera/#commonlisp - IRC Chatlog
Search
22:57:27
char
scymtym, Bike: I noticed that you changed the license on trivial-with-current-source-form. Any particular reason for that?
23:00:05
scymtym
char: etimmons said they couldn't use the system at work due to the license. are you asking for any particular reason?
23:28:06
kakuhen
silly valley is probably not interested in "stealing" lisp code, and even if they are, they probably want Clojure, not Common Lisp.
1:42:31
char
What is the expected behavior to call a function that has both &optional and &key without providing all optional but providing key?
1:44:29
White_Flame
SBCL even gives you a style warning when you define a function that way, but it's not illegal
1:45:10
White_Flame
just consider that the keywords are in the same &optional scope as your optionals, so yeah in-order fill-in
1:45:46
White_Flame
(the keyword list being one of the optional things, its contents obviously being non-positional)
1:46:45
jcowan_
†IMO use &optional *or* &key, not both. "Entweder transsubstantiation oder consubstantiation but in no case subsubstantiation." --my cousin James
2:02:39
pjb
char: notably in CL there are 2 functions that have both optional and key arguments, and they're a known pitfall.
2:08:20
pjb
write-string, write-line, parse-namestring and there's also a macro: with-output-to-string.
3:15:36
kakuhen
Does anyone know here if there has been an attempt to provide a common lisp interface for Audio Units or VST?
3:40:55
pjb
kakuhen: AFAIK, not. Note that VST 3 API is a C++ API. This makes things more difficult.
3:41:50
pjb
kakuhen: also, VST is designed to make plug-ins, and it's difficult to make a plug-in in CL. You'd have to use ecl, and generate a library, and load libecl.so along.
3:42:26
pjb
kakuhen: clasp which integrates "natively" with C++ would be nice, but I think it lost the ability to generate libraries like ecl can.
3:42:44
kakuhen
but I have a reference book on Core Audio and it's pretty complicated (for me at least)
3:42:52
kakuhen
a lot of basic data structures it uses, I dont know how you'd make the equivalents on Lisp
3:43:12
pjb
kakuhen: one solution would be to implement a VST module that would forward stuff on a socket, and have a CL process connected to do the job. of course, it would then be much less efficient. Perhaps going thru shared memory would be feasible.
9:52:38
Guest63
Appears I have to run (named-readtables:in-readtable cmu-infix:syntax) in REPL and cannot just run it as part of a file
10:05:39
phoe
a file-only IN-READTABLE only affects the file compiler, same as a file-only IN-PACKAGE
10:08:42
Guest63
Does it cascade down in a file? E.g. if I have a file with the above, and then have a "(load ...)", will the file loaded have it?