Re: ASDF: module and system level dependencies don't work right?

Todd Sabin <[email protected]>
Newsgroups gmane.lisp.cclan.general
Message-ID <[email protected]>
[email protected] writes:

>>>>>> "GK" == Gary King <[email protected]> writes:
>
>     GK> Hi Todd,
>     GK> I like things the way they are though documenting the behavior  
>     GK> explicitly would be good. To my mind each module is a separate  
>     GK> "piece" and the flow of dependencies should stop at each boundary. On  
>     GK> the other hand, dependency ought to flow between the files within a  
>     GK> module. I don't have a good justification for this but it seems  
>     GK> reasonable enough to me and fits my mental model.
>
> But how does this work if there are modules that contain macro
> definitions that are consumed downstream?

Yes, this is the main problem that I have, though I don't think it's
limited to macros.

> I suppose one answer is "just don't that."  If everyone thinks that's
> a good answer, then just documenting it would be enough.

That would be pretty unsatisfactory from my point of view.  I have a
bunch of utility macros (e.g. with-gensyms, etc) that I use in totally
unrelated systems.  The only logical thing seems to be to put their
definitions in a 'utilities' system, and have everything else depend
on that.  How do others handle that situation?

> Is there a clear description (even intuitive) of the intended behavior
> of the :force argument?

I've looked at it some more, and think I understand it now.  The
things you can specify with :force (I think):

nil - force nothing (the default)

t  - force everything, but only in the system named in the operate command

a list of system specifiers - force everything within the named systems

any other atom - force everything, in this and systems depended on

-- 
Todd Sabin                                          <[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.