On Fri, Feb 1, 2013 at 8:19 PM, Anton Vodonosov avodonosov@yandex.ru wrote:
01.02.2013, 23:23, "Faré" fahree@gmail.com:
After discussion with people on #lisp and via private chat, I decided to use a shorter name. Here is what was released in 2.27:
:long-name "Another System Definition Facility" :homepage "http://common-lisp.net/projects/asdf/" :bug-tracker "https://launchpad.net/asdf/" :mailto "asdf-devel@common-lisp.net" :source-control (:git "git://common-lisp.net/projects/asdf/asdf.git")
Another useful slot would be :purpose, it could specify what the library is: web server, db client, image processing library, data-structures library, etc.
The values in this slots are tags from some specified taxonomy. To avoid creating the taxonomy from scratch we could start for example with the tag tree from cl-user.net.
In in the future we could want to improve the taxonomy. If the new improved taxonomy is incompatible with the old one, we can then introduce new slot, :purpose2, specifying that it can hold values from new taxonomy.
I think this is an idea for future, it's probably too big to be in the scope of ASDF3 s
Why not. And if some people end up actually using component-property for such useful purpose, or otherwise make successful use of it, I am willing to reconsider the deprecation of component-property, and/or my successor will.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org No matter what language you use, a Sufficiently Smart Compiler(TM) will be able to find an efficient implementation for whatever apparently difficult problem you specify. However, a Sufficiently Smart Compiler(TM) for arbitrary problems is itself an AI-complete problem.