On 6/28/16 Jun 28 -1:57 PM, 73budden . wrote:
> What about #. ?
>
One can, of course, use #. to set any part of a system definition.
But it's worth thinking about how this could go awry.
E.g., if you list all the files in the system definition, in the classic
way, and you add a file, the system
What about #. ?
On 6/28/16 Jun 28 -7:19 AM, Jan Moringen wrote:
> Hi.
>
> It seems to be a common pattern to maintain a project's version
> information as a string in a separate file, e.g. version.sexp, and use
> something like
>
> (:version (:read-file-form "version.sexp"))
>
> to get that information into
Hi.
It seems to be a common pattern to maintain a project's version
information as a string in a separate file, e.g. version.sexp, and use
something like
(:version (:read-file-form "version.sexp"))
to get that information into the system definition. This seems like a
good thing to do as long