rpgoldman at sift.info
Mon Jun 1 22:54:24 UTC 2009
Gary King wrote:
> Hi Svante,
> (Sorry for the slow response... sending to the ASDF list too)
> I sympathize with your question: "the most common thing to do with
> ASDF, why do we make that harder than necessary?" I believe that the
> answer would have been that ASDF is philosophically based on
> performing "operations" on "systems" and so it was better (in some,
> perhaps, Platonic sense) <smile>.
> I actually agree with you and think that we should add something like
> (load-op <system> &key ...)
> to ASDF public interface.
> If there isn't a lot of disagreement, I'll do that soon.
I'd like to second the motion. I've been meaning to get around to
submitting a patch that would add LOAD-SYSTEM, COMPILE-SYSTEM and
TEST-SYSTEM, with the obvious expansions to asdf:oos.
Yes, I know that the user can do this him/herself, but given that the
user inevitably will want to add the commands seems to me a strong
argument for doing it. After all, libraries are supposed to save work,
not make it!
While Kenny's review of his first experience with ASDF was, perhaps,
unhelpfully inflammatory, I do agree with the central thesis that it's
too hard to use ASDF out of the box and that we should make it easier.
> thanks for you question,
> On May 22, 2009, at 6:14 PM, Svante Carl v. Erichsen wrote:
> This is just a little question or request that has perhaps been asked
> numerous times before.
> Why is there no predefined macro for the by far most used asdf user
> Instead of (asdf:operate 'asdf:load-op 'my-system), I'd like to just
> (asdf:load-sys 'my-system).
> Best wishes,
> Gary Warren King, metabang.com
> Cell: (413) 559 8738
> Fax: (206) 338-4052
> gwkkwg on Skype * garethsan on AIM * gwking on twitter
> asdf-devel mailing list
> asdf-devel at common-lisp.net
More information about the asdf-devel