On 04/06/2015 12:10 PM, Dimitri van Heesch wrote:
> I try to keep doxygen's code very portable. As a result I have avoided using STL.
I can understand not wanting to use STL, which, despite the name, was
never really standardized, however the standard C++ library which is
part of the C++ standard definition should be portable and consistent.
Of course you noted that, though I thought stdc++ was part of the
standard before rev 11. Boost I can certainly understand leaving out.
I'm definitely not a fan of adding additional dependencies that are
outside of a standard build environment (whatever that means :-).
I had assumed that Doxygen had predated stdc++, but thought maybe there
might be some momentum to "update" it.
> Also STL uses exceptions whereas doxygen doesn't. So if any STL class throws an exception,
> doxygen will crash.
Fair enough.
> So what do you need that is in STL, but not in qtools?
I disagree with the assertion that the standard C++ library (of which
STL is a predecessor) is not portable, but it's your baby. It's not so
much that qtools doesn't have things that are unavailable, for me it's
partially a matter of familiarity. Maybe even wholly. I find qtools
confusing with its multiple implementations of string classes and so
on. Qtools does a lot of the same stuff as stdc++ but I find the stdc++
implementation cleaner and more thorough, personally.
I can certainly use the qtools, though it'd be helpful to get some
clarification as to when to use "QGString" and when to use "QCString".
The documentation of the former is just "This is an alternative
implementation of QCString", which isn't terribly helpful.
Also if you happen to have an emacs style setting that you can pass on
so I can keep the formatting consistent, I'd appreciate it :-)
|
