#229: Using a nonexistent header file should lead to an error message ---------------------+------------------------------------------------------ Reporter: hinder | Owner: Type: defect | Status: new Priority: major | Milestone: Component: Cactus | Version: Resolution: | Keywords: ---------------------+------------------------------------------------------
Comment (by hinder):
Is it necessary to require a particular capability in order to include a header file?
I thought that the two things were orthogonal. In fact, if it is possible for more than one active thorn to provide a header file, and only one thorn providing a given capability can be active at one time, it would not be possible to make the provision of a header file entail requirement of an associated capability. So the two concepts are distinct.