Re: Re: [Cclan-commits] CVS: asdf asdf.lisp,1.89,1.90

Well, go me for kicking the ant pile in CCLAN! My Christmas resolution
was going to be "have someone send some email on CCLAN," but I'll have
to think of a new one, now.

Perhaps it would be best to think of this in terms of use cases.
Emphasizing that expression of intent is important.

The use case that I have in mind is this:

Araneida :weakly-depends-on Parenscript. Within Araneida, there are
several components that load up additional behavior when Parenscript is
present.

; such as this (not in actual code)
#+parenscript(defmacro emit-css (css)
				(js:css ,css))

Currently, each system has to pushnew onto *features*, which leaves two
problems:

  The question of "should *features* be used for this at all?" is
  unresolved

  People have to have magic lines in their code.

Me? I'm opposed to magic lines. Magic lines result in magic emails to
magic maintainers which magically languish before being magically
committed.

As for the *features* question...one of the reasons I push on
:asdf-systemname is so there would be no conflict with some feature -
the most commonly cited reason for not having this in *features*.
Having to do #+asdf:parenscript would also be fine - I just didn't think
of that.

Whichever way we decide, I would like to have it so that people using a
system don't depend on maintainers updating their system for this
capability.

That is all,
Alan


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