WARNING: System definition file ...
fahree at gmail.com
Thu Oct 12 11:25:56 UTC 2017
On Thu, Oct 12, 2017 at 7:17 AM, Stas Boukarev <stassats at gmail.com> wrote:
> Yes, SBCL has a deprecation process that goes through several stages which
> span several years. QUIT signals a style-warning, not warning, and is
> unlikely to ever signal a warning and will never go away.
.asd files are load'ed and not compile-file'd so the difference
between warning and style-warning there is inconsequential.
And yes, the deprecation process for ASDF also takes many years, and
the warning won't turn into an error for at least two years to come
and maybe more. Some of the deprecated functions will probably forever
remain style-warning's. Other functions may be escalated to warnings
> If you're willing to fix all the affected systems just go through quicklisp,
> it'll have plenty. But maybe that should be done before introducing new
I've done that kind of stuff in the past and will keep doing it. The
warning is how you get things fixed. Just like with SBCL deprecation.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
[I]f we wish to count lines of code, we should not regard them as "lines
produced" but as "lines spent": the current conventional wisdom is so foolish
as to book that count on the wrong side of the ledger. — E. W. Dijkstra
More information about the asdf-devel