Re: rfc - delay the parsing of system components

Gary King wrote:
> OK. I hear what everyone is saying and appreciate the feedback. I'd  
> like to back up (or out!) a bit and reconsider my goals:
> 
> * I don't want to replace ASDF; it;s good, it works, it's in use;  
> adding a new one just muddies the waters.
> * I do want to make it easier to use extensions (new operations and  
> file types) in a system file.
> 
> My first plan was the proposal to delay parsing and muck with  
> traverse / perform. Here is two others:
> 
> 1. add keyword
> 
> * As in #0, Delay the parsing of system components (so that these can  
> come later)
> * Add a new keyword (as RIchard Kreuter suggested) that loads  
> extensions and which is processed "outside" of and before traverse/ 
> perform. Let's call it :requires

Nitpicky suggestion --- let's call it something else to avoid confusing
with the (deprecated) CL notion of require.

> * An operation will first process the requires form, then expand the  
> component forms, then run the existing traverse/perform

While we're messing with this, any chance of getting something which
wraps around the whole operation on a component so that we can, e.g.,
impose dynamic bindings around the entire load-op as applied to a
system?  I suppose that's off-topic, but the current overhaul seems like
a good opportunity to get that done as well....

This seems like the preferable solution.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/