(non-) Executable packages vs abstract

While trying to understand the implications of Bug 29210, I stumbled upon the following line in 3.5.3.3 (just after error XTSE3060):

<quote>
A package is executable if and only if it contains no component whose visibility is abstract. A package that is not executable is not a stylesheet, and therefore cannot be nominated as the stylesheet to be used when initiating a transformation.
</quote>

And the following Note:

<quote>
In other words, if a component is declared as abstract, then some package that uses the declaring package of that component directly or indirectly must override that component with one that is not abstract. It is not necessary for the override to happen in the immediately using package.
</quote>

I can't directly recall the decision or find it in the spec, but I believe we have, at some point, allowed abstract components to exist, as long as these components are not used. As such, I think this line is a remnant from an earlier cleaning up and should be removed.

Reported first to the list as I'm not sure, if you agree it is a bug, I will report it as bug so it can be tracked.

Cheers,
Abel

Received on Monday, 19 October 2015 22:45:22 UTC