I’m documenting a framework with several class clusters. Each has a
header with an abstract class declaring core functionality, and one or
more categories declaring derived functionality, similar to the class
clusters in Foundation kit. For instance:
I’d like to have the headerdocs for the Foo(Additions) category
methods rolled into the headerdocs of the Foo methods. As it is,
Foo(Additions) is treated as a separate class defined in the same file.
As I see it it would make sense for the desired functionality to be
invoked if I put an /*! @class Foo */ declaration before the category,
but this is currently treated the same as /*! @class Foo(Additions) */,
i.e. the category is treated as a separate class. (If I don’t put in an
@class at all, the methods end up in the file context rather than a
Do not post admin requests to the list. They will be ignored.
Headerdoc-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden