LISP ASDF:Shit-Up-My-Code

(require 'asdf)
(asdf:operation 'asdf:load-op 'my-library)

What is this faggotry? How do I make it transparent, so that I can just (require 'my-library) and have it just work?

There's a "code as data" philosophy in Haskell, too. It's not related to macros, though, but rather to writing small, very specialized interpreters (EDSLs basically). You define a data type that represents the AST of your EDSL and then add some functions for evaluating that AST.

I might add that this is better than Lisp's macros, because macros aren't first-class citizens. You can't pass macros as arguments to higher-order functions like map or filter.

Have you seen Common Lisp? It has more syntax than Haskell.

not using quicklisp

mmy face when

le epic lols xD

I figured it out, Quicklisp can load local systems and takes care of all of that nonsense.

Once I've set up the path in the ASDF registry to my library's system definition, all I have to do once is:

(ql:quickload "my-library")

>>4
Yeah, just found out that quicklisp wraps asdf and makes asdf-install deprecated, was reading some old docs. I'm new to Common Lisp, I'm coming from Scheme. I got tired of all of the non-standard libraries and differences between the different Schemes.

>>2
Any language can do that though.

>>7
Can any language pre-emptively check >>11-kun's dubs?

>>9
Nobody's getting any consecutive integers here.