- asdf-devel - mailman3.common-lisp.net

[asdf-devel] Slight unportability in %DEFINE-COMPONENT-INLINE-METHODS
by Tobias C. Rittweiler 06 Sep '09

06 Sep '09

%DEFINE-COMPONENT-INLINE-METHODS contains the following LOOP form: (loop for data = rest then (cddr data) while data for key = (first data) for value = (second data) ...) However, if you look at LOOP's BNF in the specification, you'll see that termination clauses *must* appear after :for clauses. CLISP rightfully signals a warning. -T.

5 4

[asdf-devel] [OT] Git resources
by Daniel Herring 31 Aug '09

31 Aug '09

Here are a few links that might be helpful to people learning git. Its culturally different than CVS; but once you learn it, there's no turning back. The ability to experiment with local branches, back up, rewrite history, and only publish the sanitized history is quite liberating. http://tomayko.com/writings/the-thing-about-git http://progit.org/book/ http://git-scm.com/documentation http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html http://www.kernel.org/pub/software/scm/git/docs/everyday.html http://www.kernel.org/pub/software/scm/git/docs/user-manual.html My suggestions - always have `gitk --all` loaded for the repo you're working on - update (not reload) gitk after modifying any branches or tags; this leaves the old objects displayed - `git reset --hard $OLDSHA1` can clean many messes, letting you try again. - reload gitk to hide deleted branches you're comfortable with losing - learn by playing around with local clones of a larger repository - install some of the git contribs, especially git-completion.bash and git-new-workdir Later, Daniel

3 2

[asdf-devel] announce: asdf 1.361
by Gary King 27 Aug '09

27 Aug '09

This release includes the not very well tested window's shortcut handling code that Daniel Herring patched into his version and I merged into the mainline. It also includes several documentation fixes from Robert Goldman and fixes the issue Faré noticed with respect to `nil` values in sysdef-central-registry-search. From the [changelog][]: * Merge with Daniel Herring's Windows link patches * add \*resolve-symlinks\* defvar to determine whether or not ASDF should resolve symlinks when determining a system's pathname * rather than raising an error, silently ignore `nil` values in the sysdef-central-registry-search. * pull system pathname determination logic out of defsystem and into `determine-system-pathname` function * tweak documentation [changelog]: http://common-lisp.net/project/asdf/changelog.html Enjoy, -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0

[asdf-devel] Quick asdf.texinfo patch
by Robert Goldman 27 Aug '09

27 Aug '09

I noticed today that the defsystem grammar info node does not include the :class option. The attached patch fixes that. diff --git a/asdf.texinfo b/asdf.texinfo index cfef5c6..b539182 100644 --- a/asdf.texinfo +++ b/asdf.texinfo @@ -339,7 +339,8 @@ option := :components component-list | :operation-done-p method-form | :depends-on ( {dependency-def}* ) | :serial [ t | nil ] - | :in-order-to ( {dependency}+ ) + | :in-order-to ( {dependency}+ ) + | :class symbol component-list := ( {component-def}* )

2 1

[asdf-devel] Loading another system for an operation?
by Robert Goldman 27 Aug '09

27 Aug '09

Here is a case that I haven't encountered before using ASDF, that seems like an interesting one: Imagine that you have a system S, with a new component class, C in it. Further there is an operation O that you MAY need to perform on the components of class C. In order to perform operation O on C, you need to have system S1 loaded. However, if O is unnecessary, then you don't need to load S1. In this case, S does not really depend on S1. You only want to load S1 if there's some component of class C such that the operation-done-p test on O and C fails. Otherwise S1 should not be loaded. So how do we record this dependency? I had thought of attaching it to the actual method of component-depends-on for O and C, but that won't work because when we look up the name of S1, it will be relative to C's parent, so ASDF will be looking for components of S, not for other systems.... I can break that with an around method on FIND-COMPONENT, but thought that might be the wrong thing.... If I was to attach the dependency to performing the operation O onto the system S, then I believe S1 would always be loaded --- unless I record that operation-done-p O S is T if operation-done-p is T for all of the children of class C. That may be the right thing to do, but seems quite cumbersome. This seems like it would be a common use case -- the dependency is really a dependency for the transformation, not for the code that's actually loaded -- so I'm wondering if anyone's encountered it before and handled it more elegantly than I am... Cheers, r

1 0

[asdf-devel] announce: ASDF 1.359
by Gary King 24 Aug '09

24 Aug '09

Patch for system-source-file from Greg Pfeil * system-source-file now works for systems without their own .asd * moved defgenerics to their own section because I like it that way. Documentation improvements * added docstring to the method-combination standard-asdf-method- combination * added docstring to the generic-function traverse * added description of `test-op` to the manual * removed descriptions of test-system-version operation and feature- dependent-op thanks to all, -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

4 7

[asdf-devel] contradiction in ASDF central-registry default vs code
by Faré 21 Aug '09

21 Aug '09

The default for ASDF's *central-registry* in SBCL contains a (let (...) (when ...)) which can and *will* return NIL in some cases (i.e. when an executable SBCL image is run). On the other hand, sysdef-central-registry-search calls directory-pathname-p on each entry, which assumes that NIL is an invalid entry. My proposed solution: directory-pathname-p should check that its argument is indeed a pathname designator. [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Computerese Irregular Verb Conjugation: I have preferences. You have biases. He/She has prejudices.

3 4

[asdf-devel] ASDF features under discussion
by Gary King 19 Aug '09

19 Aug '09

For the record, we've had recent (but not definitive) discussions of: * whether or not optional parts of a system should be `nil` or unbound * version numbering * integrating ASDF and testing * ASDF and the windows symlink patch. If there are things I missed in the above list, please let me know. thanks, -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

2 1

[asdf-devel] Announce: ASDF 1.360 (sorry for the churn)
by Gary King 19 Aug '09

19 Aug '09

I realized belatedly that CLISP wants (setf documentation)s to come after the thing that it is getting the documentation. Fixed. -- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM * gwking on twitter

1 0

[asdf-devel] Windows shortcuts
by Robert Goldman 19 Aug '09

19 Aug '09

Apparently, some time ago David Lichteblau proposed an asdf patch (which I am attaching) that would make it possible for ASDF to follow Windows shortcuts as if they were symbolic links. Does anyone know why this didn't make it into ASDF? Should we apply this patch? I'm just about to give a quick talk on ASDF, and I'm not looking forward to telling the Windows folks that it won't work that well for them.... Cheers, r

3 4