On Sun, Apr 18, 2010 at 4:32 PM, Robert Goldman rpgoldman@sift.info wrote:
On 4/17/10 Apr 17 -6:10 PM, Juan Jose Garcia-Ripoll wrote:
- The parsing of DEFSYSTEM currently can not be customized by the class.
With all due respect, this is at one and the same time not true, and the way it should be(!) [...]
- I am surprised to hear you, of all people, call for allowing ASDF
extensions to customize the parsing of DEFSYSTEM, since this seems to directly contradict your desire for ASDF to become more declarative
I realized that, as usual, I did not express myself properly. I should have not split the two points in DEFSYSTEM and SHARED-INITIALIZE.
My actual complain was that there is no way to add options to a class and let the class process the system definition based on them. Not really the parsing: if DEFSYSTEM is implemented using SHARED-INITIALIZE and the class gets the original form, then it could implement additional parsing steps, such as ensuring that there is a configuration file for lift, or placing some safety actions before and at the end of the test system.
I am not at all for classes changing the DEFSYSTEM grammar, or introducing hidden dependencies themselves. That would go against any effort on turning system definitions into descriptive files that can be processed independently of any configuration one may have.
Thanks a lot for clarifying this point.
Juanjo