On Fri, Jun 5, 2009 at 5:05 PM, Ville Voutilainen
> On Thu, Jun 4, 2009 at 6:02 PM, Erik Huelsmann <ehuels@...> wrote:
>> One comment regarding our 0.15 release which I'm about to cut: We need
>> to make MACROEXPAND-ALL and COMPILER-MACROLET publicly available in a
>> package. Currently they are internal in the SYSTEM package, which
>> probably isn't good enough.
> Here's a stab at macroexpand-all. I'm a complete novice/layman at lisp
> packages, so
> I'm not at all sure what I'm doing here. :) Comments welcome, I'll cook together
> a patch for COMPILER-LET shortly.
Imho it depends on who's the "owner" of those symbols. If they're in
:system because other code in system uses them, perhaps it would be
better to keep them defined in system and in addition import and
export them from :ext. Otherwise, if they are in :system "by
accident", they can safely be moved in ext altogether. As a matter of
strict personal preference, I tend to avoid having multiple in-package
forms in the same file, but that's just me.
Just my €.02