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 …
For packages, I use keywords, and for lists of exported symbols in defpackage I use uninterned symbols. These help for portability to mlisp
-
-
Portability to alternate readtable-cases is why I am a bit surprised. Usually, you can't go wrong using a symbol for a string designator.
-
ASDF is uniformly downcasing symbols on all implementations. Names are not interned symbols but strings that are keys of a table.
- 4 more replies
New conversation -
-
-
Why prefer keywords to uninterned symbols?
-
Sharing. Package names ARE going to be repeated by many clients. Symbol names will hopefully be used once, optimized away into strings.
- 1 more reply
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!