bug: after erring on undefined component type, system is reported to load successfully

Faré fahree at gmail.com
Sat Jan 9 00:15:42 UTC 2016

This is an issue with how ASDF parses systems, one of the few parts
that ASDF still does mostly the same way that ASDF 1 did. Can you open
a bug on launchpad? You're not the first to mention this bug in error

I suppose the correct thing to do without a big refactoring would be
to either have a successfully-parsed-p flag in the system that is
checked at opportune moments, or to have a unwind-protect somewhere to
de-register the system if it was incorrectly parsed.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Your conscience never stops you from doing anything.  It just stops you
from enjoying it.

On Fri, Jan 8, 2016 at 6:03 PM, 73budden . <budden73 at gmail.com> wrote:
> Version 3.1.5,
> Example system definition:
> (defsystem :s3
>   :components
>   ((cl-user::cons "file-name-does-not-matter")
>    ))
> ;; eof
> I try to load it, it says:
> "Error while trying to load definition for system s3 from
> pathname c:/clcon/lp/test/s3.asd:
>    don't recognize component type CONS"
> Then I try to load it another time, it says:
> T

More information about the asdf-devel mailing list