Dependency across systems
Bug #1294035 reported by
Faré
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ASDF |
New
|
Undecided
|
Unassigned |
Bug Description
ASDF1 and ASDF2 did NOT allow a component to depend on anything but a direct sibling. ASDF3 will let you specify that, if you define a component-
Should we allow it? Some bundle operations will get it wrong, but maybe they deserve it.
Cheers,
—♯ƒ • François-René ÐVB Rideau •Reflection&
If you're a quiet, law-abiding citizen most of the time but occasionally cut
someone up and bury them in your backyard, you're a bad guy.
— Paul Graham, "The Power of the Marginal"
To post a comment you must log in.
What would be the means of prohibiting people from doing this? We could make COMPONENT- DEPENDS- ON be a function instead of a generic function, I suppose (that sounds hard), or not export it from ASDF/INTERFACE (this would not absolutely prevent specialization, but would warn people who do specialize that we reserve the right to break their code).
Is that what you have in mind?