On Mar 20, 2011, at 12:47 PM, Kevin Downey wrote: > I am no python programmer, but if you look at > http://docs.python.org/library/socket.html you see it passes in the > number of bytes you wish to receive on a call to the receiv method on > a socket. With that in mind parsing nrepl messages becomes a huge > pain. At no time when parsing a nrepl message do you know how many > bytes you need. The messages start with a string representation of a > number (variable width) and the rest of the message is some set of new > delimited strings.
FWIW, a hello-world-level interaction with an nREPL server from python: https://gist.github.com/de3b8d0ecdccf6655a63 You don't need to know how many bytes you need when parsing an nrepl message, which would seem to be an advantage to me. > I thought you were just advocating for ditching slime because it's not > clojure centric enough, how does python fit into this? I've never advocated "ditching slime", I've been advocating for a network REPL suitable for use by any and all Clojure tooling. My mentioning python was just an example of a non-Clojure runtime from which one might want to talk to a Clojure/JVM process running a network REPL server. - Chas -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
