4 ms·

> I bet you won't find any or less than 2% of the entire codebase One can look from another angle into some code bases: https://github.com/McCLIM/McCLIM/blob

by lispm 5y ago

> I bet you won't find any or less than 2% of the entire codebase One can look from another angle into some code bases: https://github.com/McCLIM/McCLIM/blob/master/Examples/stopwatch.lisp https://github.com/McCLIM/McCLIM/blob/master/Examples/stopwa... It uses a ton of complex macros: Built in macros: DEFPACKAGE, DEFMETHOD, MULTIPLE-VALUE-BIND, LOOP, ... Language extensions: WHEN-LET, ... Library macros: WITH-OUTPUT-AS-PRESENTATION, FORMATTING-TABLE, DEFINE-APPLICATION-FRAME, ... Even a generated macro: DEFINE-STOPWATCH-COMMAND (which was defined by DEFINE-APPLICATION-FRAME)

smnplk 5y ago
There is only one custom macro definition in this code, 10 lines of code without docstring. Builtin macros are not an issue, why would that be an issue ? Those are just part of the language standard library. It's the same as when you use reserved words in other languages, like *import* statement in golang or *ns* macro in Clojure, it's just part of the language and you learn how to use it. I was talking about custom macros. Disclamer: My goto lisps are Clojure and Janet, so I am not very familiar with CL.