> On 25 Apr 2017, at 14:09, Alberto Mardegan <[email protected]> > wrote: > > On 25/04/2017 09:29, Martin Smith wrote: >>> What would be incorrect as those APIs are only internal for C++, but >>> public for QML or v.v. >> >> Then we need \cpponly and \qmlonly, or something like that. > > This is calling for future headaches, when you start adding python or > other languages. > > It's better to just support using \cpp, \qml, \python tags; and if no > tags appear, then it's assumed that the documentation applies to all > languages. > Also \nocpp, \noqml and \nopython could be useful.
Or something with a parameter like \lang(cpp) \lang(qml) etc. might be more extensible? (not sure of what sort of syntax like that you can support inside a backslash doc tag… should follow the convention if there is one) _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
