| mdawson | |
| dfaure |
| Frameworks |
Better specify the requirements the parent class needs to have.
KConfigCompiler generates different variants of ctors taking either:
In order to have Inherits generate compiling code in all cases the
parent class needs to provide accessible ctors.
This change updates the docuementation to reflect this.
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
| src/kconfig_compiler/README.dox | ||
|---|---|---|
| 111–115 | an ctor -> a ctor. Also, would it make sense to explain here what those arguments are, or is that explained later? | |
| src/kconfig_compiler/README.dox | ||
|---|---|---|
| 111–115 | Also, "empty ctor" sounds like the body should be empty. I think you meant "a default constructor". (BTW I would spell out "constructor" instead of using an abbreviation) Nicolas: indeed it's not clear what the QString is, in this sentence, so rather than duplicating the API documentation for KConfigSkeleton, I suppose this could say: "and must provide a default constructor, a constructor taking a QString argument (see the one in KConfigSkeleton), and a constructor taking a KSharedConfig::Ptr as argument (see the one in KConfigSkeleton)." | |
| src/kconfig_compiler/README.dox | ||
|---|---|---|
| 112 | Missing a '(' somewhere, most likely before kcfgfile. | |