Re: Order of *CENTRAL-REGISTRY* traversal
Nikodemus Siivola <[email protected]>
| Newsgroups | gmane.lisp.cclan.general |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 9 Dec 2005, Gary King wrote:
> I like the level of abstraction but think that asdf:*central-registry* should
> not be at all exposed. I'd vote for
I think the cat's already out of the bag on that one :/
*CENTRAL-REGISTRY* could be depracated, but as long as it people are still
using it it all of the new layers on top of it aren't very robust.
While I'm by no means opposed to incremental API improvements to ASDF I do
have the feeling that before tinkering with things too much it would be
better to make a clean break and call the new design (whatever it may be)
ASDF2: the installed base of ASDF is way past the mythical 12 of "make".
;-)
In either case: it turns out that the ASDF API _can_ express what I needed
to express. Essentially:
(defun sysdef-priority-search (name)
(let ((*central-registry* (list '(my-systems-pathname))))
(sysdef-central-registry-search name)))
(push 'priority-search *system-definition-search-functions*)
Kudos to Dan for making ASDF the extensible flexible beast it is!
Cheers,
-- Nikodemus Schemer: "Buddha is small, clean, and serious."
Lispnik: "Buddha is big, has hairy armpits, and laughs."
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click