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

"Robert P. Goldman" <[email protected]> writes:
>     >> Is there a clear description (even intuitive) of the intended behavior
>     >> of the :force argument?
>
>     TS> I've looked at it some more, and think I understand it now.  The
>     TS> things you can specify with :force (I think):
>
>     TS> nil - force nothing (the default)
>
>     TS> t - force everything, but only in the system named in the
>     TS> operate command
>
> Is this really the effective semantics of T?  It doesn't seem like it
> to me.  I just tested by doing:
>
> (asdf:oos 'asdf:load-op :shop-airport :force t)
>
> on this system definition:
>[...]
> and all of the depended-on systems were recompiled...

Right, sorry.  I remember now.  The options I described are what the
intent appears to be, based on some of the code and comments.  But the
code that actually checks for whether something is forced or not
doesn't jibe with the rest of it.  I missed that the second time
around.

That's probably a bug, but since :force is undocumented it's hard to
say.

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