Re: Re: [Cclan-commits] CVS: asdf asdf.lisp,1.89,1.90
Alan Shields <[email protected]>
| Newsgroups | gmane.lisp.cclan.general |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Dec 07, 2005 at 05:18:22PM +0000, Christophe Rhodes wrote: > > 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. > > If you weren't aware that #+asdf::parenscript is possible, you might > also not be aware that > #+#.(cl:if (cl:find-package "PARENSCRIPT") '(and) '(or)) > is possible too. Yes, it's a bit longer, but it is build-system > independent... Yes, I'm aware of that one. The trouble is not only that it's "a bit longer" - it's also not very clear. I mean, we don't HAVE to have #+ and #- either...but they're not just syntax sugar, they also express intent. That's the view that I'm approaching this problem from - I know it's not the only consideration. 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