WARNING: I’m about to stop using the :export option to DEFPACKAGE for good… #lisp
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.
-
-
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.
-
Some might say the purpose of package declarations is to give an external view independent of internal details. Having to see or execute internal code to know that view is at best tangled. In your heart, I think you know it fights good style and tweeted to be talked out of it.
- 3 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!