00:13:39 jangle [~jimmy1984@pool-173-67-27-249.bltmmd.fios.verizon.net] has joined #ccl 00:29:32 greetings all. where can I read more about exposing external application functionality to my common lisp environment? For instance, my application consumes sensor data and perpares it to be human viewable by arranging things etc, so that it is easy to make bitmap snapshots. I'm wondering how to best go about exposing this to common lisp. Do I have to make a shared library, essentially a thread aware set of access functions, (bu 00:29:33 where do I put the data structure?) and then and then I'm getting a little lost 00:31:19 If you want your C code to run in the same process and address space as your lisp code, then you need to wrap it in a shared library. Or you could make it a separate process and use some sort of interprocess communication to pass the data. 00:32:33 In the first case, the data will be malloc'd on the C heap. Maybe lisp will copy some or all of it into lisp objects. Depends on what the lisp code wants to do with it 01:03:28 -!- DataLinkDroid [~DataLinkD@1.146.1.181] has quit [Quit: Disconnecting -- bye] 01:14:11 -!- aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has quit [Quit: aspires] 01:19:28 i would have to run my original application separately in order for the data to be generated, at least, at the moment 01:28:58 jangle: you can use CFFI to call C functions 01:29:21 you can use uiop:run-program to call external programs and grab their output 01:30:11 it's portable, too (though most windows implementations have bugs) 01:31:14 fare: so I'm proessesing data as it comes in, and I'm looking to expose the output of intermediate steps to lisp code to play with. 01:31:33 would that be a pipe? 01:31:51 it one the master process of the other? are you talking to a daemon? 01:31:59 all in one application 01:32:08 I fire one application, consume network data, process it 01:32:40 is it the lisp application or the C application? 01:32:46 the c application 01:32:56 and its written in c++, so I guess it makes a difference 01:33:01 a small one 01:33:05 a large one 01:33:18 so you C++ application can spawn the lisp application, feed it data, and get it back 01:33:47 hmm 01:33:52 (I'm sure some C++ library does that, though I couldn't say which; possibly boost something) 01:33:56 well. 01:34:10 do you expect that I'd be passing data back and forth over standard io? 01:34:15 or you can compile you Lisp application with ECL or CLISP and link that into your C++ application 01:34:29 that's one simple possibility 01:34:39 well this is goo, i've been trying to figure out exactly what that means. 01:34:41 or you can have a lisp server and talk using sockets 01:35:08 goo, as in the lisp-like programming language that dynamically compiles to C? 01:35:08 embedding ecl or the like, what exactly does that do? 01:35:15 good* 01:35:51 I'm glad you mentioned ECL because I've been trying to figure out what it is, so I can understand how I might leverage it 01:35:52 it means Lisp and C++ live in the same image, so there's less useless copying of data and crossing of process barriers 01:36:14 (but ECL has less support for debugging and is less optimized) 01:36:32 ecls.sourceforge.net 01:36:50 the maintainer just went into mostly inactive mode 01:36:59 and is looking for a new maintainer 01:37:03 so I would look to get a repl (in ecl or clisp) that has in its envorinment, functions and data that my c/c++ code built 01:37:06 yea I read about that 01:37:17 maybe we should take it to #lisp - this is not #ccl specific anymore 01:37:26 ok 01:47:05 aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has joined #ccl 02:11:01 -!- aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has quit [Quit: aspires] 02:28:11 aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has joined #ccl 03:47:53 -!- aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has quit [Quit: aspires] 03:49:12 aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has joined #ccl 04:03:47 -!- aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has quit [Quit: aspires] 04:07:06 aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has joined #ccl 04:10:02 DataLinkDroid [~DataLinkD@1.146.153.82] has joined #ccl 04:28:37 -!- Vivitron [~Vivitron@c-50-172-44-193.hsd1.il.comcast.net] has quit [Ping timeout: 272 seconds] 04:31:53 -!- rme [rme@BCE091D5.78A1BA07.699BA7A6.IP] has quit [Quit: rme] 04:31:53 -!- rme [~rme@50.43.148.144] has quit [Quit: rme] 04:47:43 -!- Fare [~fare@cpe-69-203-115-132.nyc.res.rr.com] has quit [Read error: Operation timed out] 04:51:39 -!- aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has quit [Quit: aspires] 04:51:56 ln [~ln@84.233.246.170] has joined #ccl 05:07:16 dcooper8 [~dcooper8@c-98-250-10-50.hsd1.mi.comcast.net] has joined #ccl 05:13:33 aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has joined #ccl 05:16:59 -!- ln [~ln@84.233.246.170] has left #ccl 05:34:40 -!- aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has quit [Quit: Adios] 05:34:56 aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has joined #ccl 05:51:03 -!- DataLinkDroid [~DataLinkD@1.146.153.82] has quit [Quit: Disconnecting -- bye] 06:02:17 -!- aspires [~aspires@c-76-21-57-49.hsd1.ca.comcast.net] has quit [Quit: sudo making a sandwich] 06:35:30 -!- dcooper8 [~dcooper8@c-98-250-10-50.hsd1.mi.comcast.net] has quit [Quit: dcooper8] 08:43:42 ogamita [~t@LNantes-156-76-35-103.w82-127.abo.wanadoo.fr] has joined #ccl 09:19:11 DataLinkDroid [~DataLinkD@101.161.69.54] has joined #ccl 09:26:33 -!- ogamita [~t@LNantes-156-76-35-103.w82-127.abo.wanadoo.fr] has quit [Ping timeout: 272 seconds] 09:46:01 ogamita [~t@LNantes-156-76-35-103.w82-127.abo.wanadoo.fr] has joined #ccl 09:52:59 -!- ogamita [~t@LNantes-156-76-35-103.w82-127.abo.wanadoo.fr] has quit [Ping timeout: 248 seconds] 10:39:55 ogamita [~t@LNantes-156-76-35-103.w82-127.abo.wanadoo.fr] has joined #ccl 10:46:28 -!- ogamita [~t@LNantes-156-76-35-103.w82-127.abo.wanadoo.fr] has quit [Remote host closed the connection] 10:52:08 -!- DataLinkDroid [~DataLinkD@101.161.69.54] has quit [Quit: Bye] 12:24:12 segv- [~mb@95-91-243-233-dynip.superkabel.de] has joined #ccl 12:42:29 rme [~rme@50.43.148.144] has joined #ccl 13:05:57 -!- alms_ [~alms_@209-6-130-32.c3-0.bkl-ubr1.sbo-bkl.ma.cable.rcn.com] has quit [Quit: alms_] 13:16:09 ogamita [~t@LNantes-156-76-35-103.w82-127.abo.wanadoo.fr] has joined #ccl 13:51:26 alms_ [~alms_@209-6-130-32.c3-0.bkl-ubr1.sbo-bkl.ma.cable.rcn.com] has joined #ccl 13:53:26 -!- jangle [~jimmy1984@pool-173-67-27-249.bltmmd.fios.verizon.net] has quit [Quit: jangle] 14:01:05 aftershave [~textual@h-136-25.a336.priv.bahnhof.se] has joined #ccl 14:01:25 Fare [~fare@cpe-69-203-115-132.nyc.res.rr.com] has joined #ccl 14:42:54 jangle [~jimmy1984@50.241.129.73] has joined #ccl 15:36:54 jangle__ [~jimmy1984@50.241.129.73] has joined #ccl 15:37:31 -!- jangle [~jimmy1984@50.241.129.73] has quit [Ping timeout: 248 seconds] 15:37:31 -!- jangle__ is now known as jangle 16:09:08 -!- Fare [~fare@cpe-69-203-115-132.nyc.res.rr.com] has quit [Ping timeout: 240 seconds] 16:31:25 aspires [~aspires@173.247.205.34] has joined #ccl 16:36:08 Vivitron [~Vivitron@c-50-172-44-193.hsd1.il.comcast.net] has joined #ccl 16:41:08 -!- ogamita [~t@LNantes-156-76-35-103.w82-127.abo.wanadoo.fr] has quit [Ping timeout: 240 seconds] 16:57:39 Fare [fare@nat/google/x-ryrofasxtcclqedb] has joined #ccl 17:34:01 dcooper8 [~dcooper8@c-98-250-10-50.hsd1.mi.comcast.net] has joined #ccl 17:39:47 -!- dcooper8 [~dcooper8@c-98-250-10-50.hsd1.mi.comcast.net] has quit [Quit: dcooper8] 18:05:56 -!- segv- [~mb@95-91-243-233-dynip.superkabel.de] has quit [Remote host closed the connection] 18:09:01 segv- [~mb@95-91-243-233-dynip.superkabel.de] has joined #ccl 18:09:16 hydan [~yaaic@ip-89-103-110-5.net.upcbroadband.cz] has joined #ccl 18:35:18 -!- hydan [~yaaic@ip-89-103-110-5.net.upcbroadband.cz] has quit [Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org] 19:08:38 -!- Fare [fare@nat/google/x-ryrofasxtcclqedb] has quit [Remote host closed the connection] 19:09:12 -!- aspires [~aspires@173.247.205.34] has quit [Quit: sudo making a sandwich] 19:15:19 ln [~ln@84.233.246.170] has joined #ccl 19:15:28 aspires [~aspires@173.247.205.34] has joined #ccl 19:15:39 -!- ln [~ln@84.233.246.170] has left #ccl 19:31:52 ln [~ln@84.233.246.170] has joined #ccl 19:32:01 -!- ln [~ln@84.233.246.170] has left #ccl 19:56:23 ln [~C6248@84.233.246.170] has joined #ccl 19:56:41 -!- ln [~C6248@84.233.246.170] has left #ccl 20:23:11 ln [~ln@84.233.246.170] has joined #ccl 21:23:50 -!- billstclair [~billstcla@unaffiliated/billstclair] has quit [Read error: Connection reset by peer] 21:49:10 DataLinkDroid [~DataLinkD@120.159.108.230] has joined #ccl 21:51:21 -!- ln [~ln@84.233.246.170] has left #ccl 21:57:03 -!- jangle [~jimmy1984@50.241.129.73] has quit [Ping timeout: 272 seconds] 23:08:40 -!- aspires [~aspires@173.247.205.34] has quit [Quit: sudo making a sandwich] 23:13:50 -!- segv- [~mb@95-91-243-233-dynip.superkabel.de] has quit [Remote host closed the connection] 23:31:23 aspires [~aspires@173.247.205.34] has joined #ccl 23:35:01 Fare [~fare@cpe-69-203-115-132.nyc.res.rr.com] has joined #ccl