13:59:03Josh_2well that makes things easier I suppose
13:59:22Josh_2it'll just get garbage collected when I'm done with it?
13:59:37Nilbywith-pointer-to-vector-data is just giving the lisp pointer to C code. with-foreign-string , with-foregin-object, etc. allocates and frees non-gc memory so it's safer
14:00:12Nilbywith-pointer-to-vector-data is kind of a hack to make things fast, and zero copy when you know it's safe to do
14:05:29NilbyYou're welcome, I've probably done too much with CFFI for my own good. The problems with with-pointer-to-vector-data is probably why it isn't mentioned in the manual.
14:06:34Josh_2Well I really appreciate the help, you have been a life saver
14:08:47NilbyIt seems like maybe I helped you make more powerful bugs (:
14:16:46NilbyLisp by itself is usually pretty safe, but With proper application of CFFI and other CL things I've managed to make Lisp crash itself, the window it's in, the window system, the OS, and even make the hardware overheat and break.
14:20:22Josh_2how do I convert a :uint32 pointer back to an integer?
14:22:41NilbyIt should usually convert automaticlly, but if it doesn't you can use cffi:translate-from-foreign
14:22:42francogrexanyone here reading this has experience with sbcl VOP?
14:28:03heisigfrancogrex: Yes, I have used VOPs a few times.
14:28:04minionheisig, memo from flip214_: DANKE!!!
14:29:59Josh_2well the C function takes an argument of type uint32_t *, so I (foreign-alloc :uint32) as pass that, but it isn't being converted back to a nice integer
14:31:53NilbyJosh_2: Ah, I guess you would normally convert that with mem-ref then
14:43:39Josh_2Now I just have to figure out why when I encrypt "test" and then decrypt it i get "test ... " followed by a bunch of random characters like #\Return
14:44:27Bikesounds like you're reading out of bounds
14:47:10NilbyJosh_2: Maybe there's a uint8 zero before those which C thinks should stop you, but Lisp is like whatever.