How to write Common Lisp in 2017 – an initiation manual
articulate-lisp.com
How to write Common Lisp in 2017 – an initiation manual
1–10 of 271 posts
Re: How to write Common Lisp in 2017 – an initiation manual
#2Short answer: don't do that, use Clojure instead. It doesn't have any of listed problems.
Re: How to write Common Lisp in 2017 – an initiation manual
#3If you're so inclined I'd make it a "living document" that gets updated as the state-of-the-art evolves. Writing CL in 2017 is not likely to change rapidly in the next decade but even compared to what writing CL was like 8 years ago it has changed enough.
Nice job.
Re: How to write Common Lisp in 2017 – an initiation manual
#4Short answer: don't do that, use Clojure instead. It doesn't have any of listed problems.
Nope, it has new problems that are (IMO) worse.
Re: How to write Common Lisp in 2017 – an initiation manual
#5If you're so inclined I'd make it a "living document" that gets updated as the state-of-the-art evolves. Writing CL in 2017 is not likely to change rapidly in the next decade but even compared to what writing CL was like 8 years ago it has changed enough. Nice job.
Re: How to write Common Lisp in 2017 – an initiation manual
#6Ah yes this is exactly what I needed. I was recently trying to start a CL project but I had trouble wading through all the outdated material, especially with regards to including external packages. Thanks for putting this together!
Re: How to write Common Lisp in 2017 – an initiation manual
#7Short answer: don't do that, use Clojure instead. It doesn't have any of listed problems.
Sorry, there is a temporary ban on speaking about clojure in OP's thread. This discussion is about Common Lisp.
Re: How to write Common Lisp in 2017 – an initiation manual
#8Short answer: don't do that, use Clojure instead. It doesn't have any of listed problems.
Nope, it has new problems that are (IMO) worse.
I have dabbled in Common Lisp over the years and am quite comfortable with it. I know nothing about Clojure. What are the problems with Clojure? I am just curious. Thanks!
Re: How to write Common Lisp in 2017 – an initiation manual
#9NICE!
Re: How to write Common Lisp in 2017 – an initiation manual
#10I'm used to languages like Python, that have a number of files that are modules, and to start a program you run one of them as an entry point.
C programs consist of a lot of files that are compiled and linked into a binary executable.
Whenever I've tried to learn CL, I couldn't really wrap my head around what the eventual program would be. You build an in-memory state by adding things to it, later dump it to a binary. How do you get an overview of what there is?
I'm just too used to my files, perhaps. Or I'm missing something.