WARNING: I’m about to stop using the :export option to DEFPACKAGE for good… #lisp
-
-
Replying to @didierverna
Bad idea: then recompiling your code on SBCL will cause an error. Better idea: use macros to keep your defpackage in sync with your declarations. See how I do it in fare-scripts, using macros from fare-utils.
1 reply 0 retweets 0 likes -
Replying to @Ngnghm
Not sure what you mean. Are you referring to package variance? Because I find that behaviour really annoying. The only drawback I see with local calls to EXPORT is that if you remove one, the symbol will remain exported for the duration of your session.
2 replies 0 retweets 0 likes
Yes, package variance is an error on SBCL and undefined behavior in the standard. If you want to support it, use uiop: define-package. And you still need support tracking of your exports as in fare-utils, that can warn you when they don't match your def(ine-)package.
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!