freenode/#lisp - IRC Chatlog
Search
21:55:34
msmith
yeah, I was under the impression that the external format option would cause the with-open-file to read the integers as bytes
21:55:52
pjb
And yes, don't laugh, but we find this kind of representation/encoding problem a lot of times, in places it shouldn't appear. People (well, "C programmers") don't understand the difference between binary and text, and that hexadecimal is a textual representation for binary, etc.
21:56:34
pjb
And worse, those idiots write data as hexadecimal textual representation and are not able to parse it back in a case insensitive manner, so you find broken middle ware in places you wouldn't believeā¦
21:57:03
Bike
if you deliberately wrote in the integers that's a more normal mistake than i was imagining, anyway
21:58:01
pjb
In lisp you have to be careful indeed, because you can write a textual representation of a sequence of bytes easily with PRINT in a text file. But it is as easy to write it in binary form with WRITE-SEQUENCE in a binary file.
22:06:57
karlosz
is there any way to check if a symbol is external in a package without do-external-symbols?
22:09:57
pjb
(multiple-value-bind (ps sk) (find-symbol (symbol-name s) p) (and (eq ps s) (eq :external sk)))
3:08:47
DataLinkDroid
ACTION wonders if there is anyone here who has any experience with using CFFI to load and call functions from an Ada 2012 standalone shared library.
3:09:49
DataLinkDroid
I'm not having much luck with my first attempt at this, even though I have tinkered with CFFI before with C libraries, successfully.
3:21:45
DataLinkDroid
ACTION created the Ada 2012 library (with exported functions according to C standard), so the issue could lie on either side.
3:23:43
DataLinkDroid
ACTION can call the Ada functions fine from C code, but Ada library initialisation seems to case the lisp to crash with a stack or memory error, which appears to be raised from within Ada land.
3:32:29
DataLinkDroid
The exception raised after library init is: raised STORAGE_ERROR : stack overflow or erroneous memory access
3:33:09
DataLinkDroid
This looks like an Ada message. So it appears to be getting itself into some kind of trouble while initialising itself.