[asdf-devel] XCVB patch for split-sequence

[Faré]

2009/10/23 Tobias C. Rittweiler <tcr at freebits.de>:
>> > >
>> > > +#+xcvb (module ())
>> > > +
>> >
>> > This is... no.  Please find some way of not infesting code with
>> > build-related metainformation.
>> >
>> OK, I'll put this much-requested feature near the top of my TODO list.
>
> If every .lisp file has to begin with such an expression, can't you
> simply introduce a file-as-module defaulting scope?
>
Not sure what you mean. Unlike say PLT module forms, the XCVB module
form does not enclose the whole file, it's just the first form in the
file, protected by a #+xcvb so you can keep compiling normally without
xcvb.

I need a place to specify the dependencies in a SEXP language, if
possible in the file itself (so I can trivially use a Make backend),
so that's the obvious solution. A non-trivial Make backend or
Make-less backend is of course possible and makes it possible to have
dependencies in a central file if you want. I'll be working on the
standalone backend next, which will use a cache of tthsum instead of
file timestamps to detect change, at which point it will be easier to
have file dependency information be centralized, for those maintainers
who consider dependency information as "pollution".

PS: I first sent my mail to the cclan-list on sourceforge, and was
surprised to receive a note redirecting me to the asdf-devel
mailing-list as its successor. What about all the cclan packages that
are not asdf? (are there any of them beside split-sequence?)

PPS: Unless it's on-topic for cclan or asdf, please follow-up to
xcvb-devel at common-lisp.net.

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Classical Liberalism: the only truly subversive ideology.