CLers, I saw a lot of ugly .asd files while addressing compatibility for ASDF 3.3, so here are "ASDF best practices" https://gitlab.common-lisp.net/asdf/asdf/blob/master/doc/best_practices.md …
There were mostly (naked) symbols, but also (lower-case) strings, keywords, gensyms. And no consistency between definitions & references.
-
-
Up to now, I generally used uninterned symbols for both systems and packages, and left any case conversion to whoever reads them...
-
For packages, I use keywords, and for lists of exported symbols in defpackage I use uninterned symbols. These help for portability to mlisp
- 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!