On Tue, Feb 26, 2019 at 8:30 AM Will Mengarini wrote:
>
> * Robert Goldman [19-02/25=Mo 15:37 -0600]:
> > Even if so, why not just add `:documentation-pathname`,
> > and then no one will have to worry about type errors?
>
> +1
>
Because adding a new slot means a new ASDF version with its own
feat
* Robert Goldman [19-02/25=Mo 15:37 -0600]:
> Even if so, why not just add `:documentation-pathname`,
> and then no one will have to worry about type errors?
+1
to me,
and also keeps a nice uniformity -- if you want the long description,
you ask for it, and you know it's a string. It also imposes a cost in
complexity with only a conjectural benefit (who would consume the new
pathname designations, and which library authors and maintainers
would suppl
The more we discuss this, the more I think it's a solution in search of
a problem. Just using the standard ASDF file-inclusion capabilities
(that Faré shows in his email) seems sufficient to me, and also keeps
a nice uniformity -- if you want the long description, you ask for it,
and you
On 20 Feb 2019, at 22:14, Faré wrote:
I've seen the pattern of using
:long-description
#.(uiop:read-file-string
(uiop:subpathname *load-pathname* "README.md"))
spread among CL libraries.
I see it only as a waste of kilobytes of data (quadrupled on 32-bit
unicode lis
use the description slot as
a one-liner, and the long-description one as some kind of abstract
about the project. My README files are usually longer, more elaborate.
Also, FYI, Quickref uses README files as an introduction section in
the generated reference manuals automatically. This is
w ASD file.
https://github.com/fukamachi/cl-project/blob/master/cl-project.asd#L33-L35
I just thought it might be useful if it could be refer by calling
'asdf:system-long-description' from REPL,
or someone would make some utility tool using long-description in the
future.
To be honest,
Sounds good to me, but I'm possibly also an old-school code bummer.
- Original message -
From: "Faré"
To: ASDF-devel , Eitarow Fukamachi
, Didier Verna
Subject: long-description
Date: Wednesday, February 20, 2019 8:16 PM
I've seen the pattern of using
I've seen the pattern of using
:long-description
#.(uiop:read-file-string
(uiop:subpathname *load-pathname* "README.md"))
spread among CL libraries.
I see it only as a waste of kilobytes of data (quadrupled on 32-bit
unicode lisps such as SBCL).
I'm told it's b
