Re: Order of *CENTRAL-REGISTRY* traversal

[email protected]
Newsgroups gmane.lisp.cclan.general
Message-ID <[email protected]>
>>>>> "NS" == Nikodemus Siivola <[email protected]> writes:

    NS> 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

    NS> I think the cat's already out of the bag on that one :/

    NS> *CENTRAL-REGISTRY* could be depracated, but as long as it people are still 
    NS> using it it all of the new layers on top of it aren't very robust.

    NS> While I'm by no means opposed to incremental API improvements to ASDF I do 
    NS> have the feeling that before tinkering with things too much it would be 
    NS> better to make a clean break and call the new design (whatever it may be) 
    NS> ASDF2: the installed base of ASDF is way past the mythical 12 of "make". 
    NS> ;-)

I tend to agree about the cat being out of the bag, so I'm ok with
having *central-registry* exposed (esp since i suppose that would let
us have > 1 registry).  But I think it would be ok to tell everyone
NOW that higher level interface functions are preferred and the old
push method is deprecated.  If we were to then remove the old method,
that would be the time for the big version bump IMHO.

r
-- 
Robert P. Goldman
Senior Scientist
Smart Information Flow Technologies (d/b/a SIFT, LLC)

211 N. First St., Suite 300
Minneapolis, MN 55401

Voice:	(612) 384-3454
Email:    [email protected]


-------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.