Re: monolithic-concatenate-source-op misses a few dependencies

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

Re: syntax-control

Hi! My 2 cents (a draft for a proposal). 1. As I said, there should be a way to set up tracing and maybe assertable preconditions that should hold before loading the system. This way we can _diagnose_ what happens. This technique should be supplied not for newer versions only, but for some old

Re: monolithic-concatenate-source-op misses a few dependencies

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

Re: monolithic-concatenate-source-op misses a few dependencies

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

Re: monolithic-concatenate-source-op misses a few dependencies

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