81–90 of 97 posts
Earlier quoted context omitted.
No. AutoCAD is written in C++. It has a crude Lisp as an extension language, but that has been deprecated years ago in favor of VBA and loadable C++ DLLs.
In 2016 Visual Lisp is still supported for AutoCAD http://usa.autodesk.com/adsk/servlet/index?siteID=123112&id=... and their Lisp forum looks busy: http://forums.autodesk.com/t5/visual-lisp-autolisp-and-gener...
Apart from Clojure (which is not LISP, really), I haven't seen end-user applications written in LISP dialects (I don't think emacs is end-user software). Scheme (and its PLT dialect Racket) was in academia for so long that it literally got "friend-zoned" and has little (read "no") use in the industry. Then again, I expected to see more Common LISP around. Paul Graham really put it right, but I guess any leverage/adva…
Maxima? I mean, it traces its lineage to the golden age of Lisp, but it's still being released. And you say Scheme was friend-zoned by the industry. While I understand why this was, it's a shame: Scheme is a very nice language, and with several high quality implementations, some excellent FFI, and finally some good library support (CHICKEN is excellent here), not to mention Racket's deluge of features and libraries (…
Earlier quoted context omitted.
Maxima? I mean, it traces its lineage to the golden age of Lisp, but it's still being released. And you say Scheme was friend-zoned by the industry. While I understand why this was, it's a shame: Scheme is a very nice language, and with several high quality implementations, some excellent FFI, and finally some good library support (CHICKEN is excellent here), not to mention Racket's deluge of features and libraries (…
Chez took too long a time to get freed. Had this happened a decade earlier, it would have been nice.
I didn't mention Chez. What's Chez got to do with it?
Earlier quoted context omitted.
Chez took too long a time to get freed. Had this happened a decade earlier, it would have been nice.
? I didn't mention Chez. What's Chez got to do with it?
Earlier quoted context omitted.
Try TXR Lisp; you will be charmed. http://www.nongnu.org/txr
Thanks kaz, but I've already got the manpage bookmarked. I haven't looked at it in-depth yet, but it seems to be awk, but better, which is pretty awesome.
How have I never heard of this "common" lisp?
If we're mistaken, or if you don't want to be banned, please email hn@ycombinator.com.
Earlier quoted context omitted.
Thanks kaz, but I've already got the manpage bookmarked. I haven't looked at it in-depth yet, but it seems to be awk, but better, which is pretty awesome.
You can also completely ignore the "awk-but-different" TXR pattern-based extraction language, and just use it as a Lisp, too. The REPL is nothing but Lisp, and code stored in ".tl" files is treated as Lisp. TXR Lisp is designed to be a nice Lisp dialect on its own, not to just fill in the gaps in another language.
Earlier quoted context omitted.
English is such an oddball in the Germanic family that I'd count it an outlier. About 40% of its vocabulary is of Latin origin, and in sum about 60% of its vocabulary is made up of loan words. A couple years ago I submitted the "Uncleftish Behaviour" here [1], which demonstrates English with only germanic words. [1] https://news.ycombinator.com/item?id=7671549 For the rest of the family, there's a lot of mutual intel…
Clojure borrows from C++, C#, Common Lisp, Erlang, Haskell, Mathematica, ML, Prolog, Scheme, Java, Racket, Ruby - according to Wikipedia. I would guess that 10% of its operator names come from Lisp. Okay, that's a wild guess. Let's look at the special forms: def-, if+, do-, let+, quote+, var-, fn-, loop-, recur-, throw-, try-, monitor-enter-, monitor-exit, ... Around three from thirteen special forms have roughly the…
Earlier quoted context omitted.
? I didn't mention Chez. What's Chez got to do with it?
Earlier accessibility of a top Scheme implementation could have helped make it more popular earlier. Just like with Smalltalk and Common Lisp before which also got into trouble because of good implementations being out of reach of most people.
Earlier quoted context omitted.
Images are not a hack. They allow us to save the state of a program and use it later. My Lisp Machine at home would not even work without it. It's the software the machine boots into. Image dumps are also a useful way to create applications or use pre-assembled program state during development. Makes faster startup times, than loading objects during start each time. Even an editor like GNU Emacs boots up a Lisp image…
They're an optimization in most dialects that support it: it's not like Smalltalk, where you can reload your app state and continue exactly where you left off.
I would be very irritated if my Lisp Machine on start would reopen all network connections... But it has a controlled restart process, where I tell Lisp what to restart on a reboot. Actually a Lisp Machine has a list in memory, where the restart tasks are kept. If the image is restarted, one of the tasks it does is to go through this list and execute the various restart tasks...