Are Boost.org & Doxygen "the best" for their jobs?

[gamaron]

Hello,

Summary
-------

Are these the best tools for the following jobs? Can anyone provide
alternatives?

Threading (and other libraries): http://boost.org/
Auto doc generator: http://doxygen.org/


Details
-------

I'm an ex-C++ programmer/designer that has come back to "the fold" after a
long hiatus doing non-programming work (program management, sales,
marketing, etc).

A couple of initial resources I am seeking include threading libraries and
an automatic-documentation-from-source-generating tool (like javadoc).
(I'll probably make a couple of other posts for other things later.)

My initial search suggests that this may be some good (if not best?)
resources/tools for the job:

Threading (and other libraries): http://boost.org/
Auto-generate docs from source: http://doxygen.org/

Can anyone offer alternatives or other suggestions? I see Doxygen lists
alternative tools to itself ( http://doxygen.org/links.html ). It's a
long list, and I'm not yet up for researching the entire set. Any
educated/experience feedback is welcome.

Thanks for any help!
-Matt

 

[Karthik Kumar]

Hello,

Summary
-------

Are these the best tools for the following jobs? Can anyone provide
alternatives?

Threading (and other libraries): http://boost.org/
Auto doc generator: http://doxygen.org/


Details
-------

I'm an ex-C++ programmer/designer that has come back to "the fold" after a
long hiatus doing non-programming work (program management, sales,
marketing, etc).

A couple of initial resources I am seeking include threading libraries and
an automatic-documentation-from-source-generating tool (like javadoc).
(I'll probably make a couple of other posts for other things later.)

My initial search suggests that this may be some good (if not best?)
resources/tools for the job:

Threading (and other libraries): http://boost.org/
Auto-generate docs from source: http://doxygen.org/

Can anyone offer alternatives or other suggestions? I see Doxygen lists
alternative tools to itself ( http://doxygen.org/links.html ). It's a
long list, and I'm not yet up for researching the entire set. Any
educated/experience feedback is welcome.

Thanks for any help!
-Matt

I used to be a Java programmer before switching to C++. Having
been used to javadoc for document generation, I prefer ccdoc since
if you are using the same javadoc tags, ccdoc is going to help you
for most of the time. So the learning curve is really small here.

As far as the boost threading is concerned, I would say it is
one of the best. Right now , the C++ standard commitee is working out
to specify a library for threads. ( Please check for Ioannis' mail
recently , pointing to the blog of Herb Sutter). But I guess it would
take sometime for the standard to be released and the implementations
to catch up with it.. So for now, Boost seems the best choice.

 

[Ivan Vecerina]

Hi,

Are these the best tools for the following jobs? Can anyone provide
alternatives?

Threading (and other libraries): http://boost.org/

Some will point to ACE as an alternative for threading, but it is
part of a larger framework (oriented towards server/networked apps).

Boost's advantage is that it is intended to be an antechamber to
the C++ standard library. Some of its components (e.g. shared_ptr)
have already been adopted, tentatively, as part of the library
extensions for the next version of the C++ standard.
[but for threading itself, options are still open...]

Auto doc generator: http://doxygen.org/

Very well supported, multi-platform, open source, and a large
community of users. It is definitely a good choice IMO.
I've been using it for about 6 years now...


hth -Ivan

 

[Markus Elfring]

Threading (and other libraries): http://boost.org/

I suggest to look at these information sources.
- http://en.wikipedia.org/wiki/List_of_multi-threading_libraries

- Article "The fall 2004 ISO C++ standards meeting" by Herb Sutter
http://pluralsight.com/blogs/hsutter/archive/2004/10/23/2972.aspx
=> recent developments of the ISO C++ front
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1680.pdf
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1687.pdf

Regards,
Markus