Comment 2 for bug 1493031
Revision history for this message
| Robert P. Goldman (rpgoldman) wrote Re: bundle: remove deprecation comment | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I don't feel that these functions can be "undprecated" until they at least have docstrings that indicate their purpose and the meaning of their arguments.
DELIVER-ASD-OP is particularly problematic. It writes an ASD file "...for delivering the system as a single fasl" What's the role of this ASD file? Is it a convenience? Is it part of the bundling process? I don't *believe* so, since I don't see any IN-ORDER-TO for this operation. What is the caller expected to do with this ASD file?
Until these functions are crisply defined, they don't deserve to be part of ASDF's API.
BUNDLE-SYSTEM seems to be particularly poorly named, since it looks like it simply produces a .ASD file, which doesn't seem to be what BUNDLING ought to be (compare with LOAD-SYSTEM, TEST-SYSTEM, and COMPILE-SYSTEM). Unless someone can explain what this does in a way that makes this a reasonable name, it will be deprecated and removed.
Note that there's no sense in which this function provides a feature that "isn't provided by other interfaces" since it's a very thin wrapper around OPERATE.