libera/#commonlisp - IRC Chatlog
Search
17:34:33
jjnkn
how to correctly generate defun with a computed name in a macro? i'm getting a function named |name| instead of just name, and don't understand why
17:37:12
bike
like if you write (defun foo ...), the symbol will have an actual name of FOO. you can try it, do (symbol-name 'defun). you'll get "DEFUN"
17:39:21
edgar-rft
jjnkn: you need (format nil "~:@(~a~)-~:@(~a~)" 'a 'b) because the default readtable-case is :UPOCASE
20:34:41
bike
jmercouris: launch-program specifically has &allow-other-keys, probably because different implementations might have their own keywords
21:42:41
_death
maybe it would've been preferable for it not to have &allow-other-keys, so that someone who wants to pass implementation-specific keys would have to specify :allow-other-keys t
21:49:10
_death
it also passes :allow-other-keys t to the implementation's run-program, which is why it doesn't signal an error
23:41:26
jmercouris
I am writing "\\\\n" to a socket and on the receving end I am only reading "\\n"
23:45:10
jmercouris
bike: I did a stupid hack to be able to write strings, so the reason you see "\\\\n" is because I had just "\\n" before, and something was getting lost on the way
23:46:17
bike
as long as we're on this topic, \n doesn't do anything special in lisp. it'll just be a backslash and then an n, so if you want a newline you're out of luck
23:47:07
jmercouris
I have this string, that I am then writing, which of course will become malforemd on the other end
23:48:45
jmercouris
so how can I have a string "hello\\nworld" and send it to the socket AS IS without my precious backslash being stripped away
23:50:06
bike
ok. well to get that from the lisp reader you'd write that as "hello\\\\nworld". but i don't know what parenscript is doing.