3 ms·
And there's no sane interoperability from an algorithmic language like Lisp to a processor-driven language like C or a spaghetti-driven language like C++. What
by numeromancer 15y ago
And there's no sane interoperability from an algorithmic language like Lisp to a processor-driven language like C or a spaghetti-driven language like C++.
What is sane interoperability? How can a processor "drive" a language? And spaghetti-driven? WTF?
This must be the result of the "release early and often" habit that is often encouraged here. He would probably do better to write in detail about something he has done or is doing, rather than write vaguely about what he has been thinking about.
- arethuza 15y agoI spent a lot of time bolting strange things onto Common Lisp systems in the early '90s through a foreign function interface and I thought it was pretty straightforward. [Note: Strange things being C++ simulations generated by Lisp code directly from systems of nth order ODEs. Other non-Lisp types also wanted to use the simulations, which is why they were in C++].
- numeromancer 15y agoThat sounds like the makings of a good essay :)
- arethuza 15y agoWhat was much more fun was the fact that we also had NeWS based user interfaces connected to our Lisp applications by some glue C/RPC code. Developing in Lisp, C and PostScript on the same codebase was a lot of fun (PostScript being surprisingly Lispish - which I would never have suspected had I not been developing in both at the same time for a couple of years.) I therefore got quite excited (in an RPN kind of way) by the reference to Forth in the "Let Over Lambda" book featuring on HN today! :-)
- neutronicus 15y agoI actually find Lisp to be head and shoulders above Perl/Python/Ruby at interfacing with C.
- deleted 15y ago[deleted]