1- Regarding eval-when, see my livejournal post:
https://fare.livejournal.com/146698.html
2- features in build files are a very bad idea, inherited from the dark
times of using REQUIRE to load code (not so portably). Please don't use
them. Avoid using putting anything but build information in
Fare et al.,
The Postmodern/usocket problem I encountered was in fact due to
cl-postgres not setting a feature flag in an :execute context:
https://github.com/marijnh/Postmodern/blob/57dc8cb4acc4599aee757e8f81999a0fa83c7111/cl-postgres/features.lisp#L8
. To digress from the list topic for half a
On Sat, Oct 14, 2017 at 1:17 PM, Robert Goldman wrote:
> Will you please clarify for my benefit, since I don't actually use any of
> the image operations.
>
> Is the problem that somewhere in the process of loading Postmodern, or one
> of its dependencies, some bit of code
Will you please clarify for my benefit, since I don't actually use any
of the image operations.
Is the problem that somewhere in the process of loading Postmodern, or
one of its dependencies, some bit of code invokes `REQUIRE`? Or is this
an issue with ASDF's `REQUIRE-SYSTEM`.
If it's the
Dear Ben,
sorry I won't be developing this feature, but I'll happily merge your
patch if you do. "Just" add support for dumping source code for a
(:require ...) dependency.
—♯ƒ • François-René ÐVB Rideau •Reflection• http://fare.tunes.org
Guns & bullets don't kill people — blood loss and organ
On SBCL 1.3.11, when producing a monolithic source concatenation with
the library "Postmodern", asdf produces a file that needs a Lisp image
to need manual calls to (require :usocket) and (require :md5) in order
to load completely.
Given:
concatenatrix.asd as:
(asdf:defsystem :concatenatrix