Fixed several issues in 2.014.7. Should make Xach's quicklisp happier, especially on ECL.
Incompatibility: I deleted system-definition-pathname. As an exported function, it is redundant with system-source-file. As an internal function, it is replaced by search-for-system-definition, which can return a system object as well as a pathname.
A cursory googling shows that system-definition-pathname is used by bese qbook's publish-op. Should I reinstate system-definition-pathname as an alias for system-source-file, or should I expect qbook to be updated if anyone ever uses it again?
Xach: please tell me which symbols you'd like exported.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] Non Omnis Moriar (Not Everything In Me Will Die). — Dr. José P. Rizal
On 4/14/11 Apr 14 -12:11 AM, Faré wrote:
Fixed several issues in 2.014.7. Should make Xach's quicklisp happier, especially on ECL.
Incompatibility: I deleted system-definition-pathname. As an exported function, it is redundant with system-source-file. As an internal function, it is replaced by search-for-system-definition, which can return a system object as well as a pathname.
A cursory googling shows that system-definition-pathname is used by bese qbook's publish-op. Should I reinstate system-definition-pathname as an alias for system-source-file, or should I expect qbook to be updated if anyone ever uses it again?
I'm inclined to think that reinstating it, and making it raise a style warning for deprecation would be best. Just on the grounds that the API should stay stable until someone masochistic enough to build ASDF 3 comes along! That way we will get fewer bug reports/questions.
cheers, r
A cursory googling shows that system-definition-pathname is used by bese qbook's publish-op. Should I reinstate system-definition-pathname as an alias for system-source-file, or should I expect qbook to be updated if anyone ever uses it again?
I'm inclined to think that reinstating it, and making it raise a style warning for deprecation would be best. Just on the grounds that the API should stay stable until someone masochistic enough to build ASDF 3 comes along! That way we will get fewer bug reports/questions.
In .8 I'm considering reinstating it, with a cerror instead of merely a warning.
And I'm the masochist, except I say "XCVB" instead of "ASDF 3".
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] My understanding of macros is expanding — Matthias Felleisen wrt the PLT Scheme module system
-
Faré -
Robert Goldman