freenode/#lisp - IRC Chatlog
Search
4:43:24
emaczen
I have a lisp function whose argument gets passed to a particular cffi:foreign-funcall which expects a struct
4:43:49
emaczen
The "struct" I pass to the lisp function gets automatically translated into a lisp list
4:45:30
emaczen
How do I stop this automatic translation, or how can I force the list to be converted back to a struct?
5:43:12
LdBeth
emaczen: then just use the ctype pointer, see https://common-lisp.net/project/cffi/manual/cffi-manual.html#Foreign-Structure-Types
8:13:28
Nilby
Grue: Probably because it wants you to use #'cddr, maybe to prevent against 'something as a typo.
8:17:22
beach
Grue`: I think it means that it is going to call FDEFINITION, perhaps in each iteration.
8:33:55
Grue`
I actually avoid using #' in my code for various reasons, so this warning was annoying
8:40:08
Grue`
' always uses top level function definition, so for example if I'm calling a function in a macro expansion I'm immune to it being redefined in flet
8:42:41
Grue`
yeah, standard functions get ' for consistency. basically I only use #' for lexical scope functions
8:50:43
Grue`
there's literally no difference in (disassemble (lambda (y) (funcall 'cddr y))) whether I uuse #' or '. So the compiler probably realizes that just means (cddr y)
8:59:26
jackdaniel
it might be that optimization of "locked" funcitons is in independent module and happens much later
10:31:36
akr
so if you pass example@example.com as the envelope, cl-smtp tries to use <example@example.com>
10:33:10
akr
the problem seems to be here: https://gitlab.common-lisp.net/cl-smtp/cl-smtp/blob/master/cl-smtp.lisp#L398
10:37:19
akr
#<SMTP-PROTOCOL-ERROR a command failed:\\ncommand: \\\"MAIL FROM:noreply@domain.eu\\\" expected: 250 response-code: 555 response-message: 5.5.2 Syntax error. w3sm148620wrp.51 - gsmtp>
10:37:21
akr
#<SMTP-PROTOCOL-ERROR a command failed:\\ncommand: \\\"MAIL FROM:noreply@domain.eu\\\" expected: 250 response-code: 555 response-message: 5.5.2 Syntax error. w3sm148620wrp.51 - gsmtp>
10:44:45
akr
there was a problem with my envelope which I fixed and then there was a problem with Google SMTP denying our requests doe to wrong IP or somesuch
10:47:55
beach
prite: There are two common ways, either "see loss" or "kloss". I use the former. I know nobody to pronounces each individual letter.
11:21:50
jackdaniel
some pronouce it c-loss, as an ultimate argument in favor of Common Lisp (and not for C). of course it sounds all the same, but it is the feeling you put into words what counts here ,)