2012/3/8 Neil Van Dyke <n...@neilvandyke.org> Thanks for taking the time to look at the problem.
It sounds like Maxima and your Racket program are both trying to be the TCP > listener. Maybe "tcp-connect" instead of "tcp-listen"? > I am fairly sure that part is correct. I do receive the welcome message from Maxima. And I took a peek in the Maxima code to see what -s does. This comment is from the Maxima code: ;; Connect Maxima to a socket which has been opened by ;; some third party, typically a GUI program which supplies ;; input to Maxima. ;; Note that this code DOES NOT create a Maxima server: ;; Maxima is the client! > Once that's working, for robustness, you might want to manage some TCP I/O > buffers yourself, and use "sync" (or "sync/timeout" or similar) on the > ports. Using the buffers also makes it easier to look for some markers in > the protocol without blocking. > I'll look into this. I did run into blocking problems in earlier versions of my snippet. > P.S., I know you used that "process" temporarily here, but for the benefit > of people who see this later, they should try to use "process*" instead, > and monitor the status of the ports and the process (possibly in the same > "sync" as the TCP ports). > Ok. /Jens Axel
____________________ Racket Users list: http://lists.racket-lang.org/users
