search for: 1_37_0

...eptions, some > with, and the results are linked together. At the best case, it > would complicate our build system to be able to support different > set of flags for building LLVM libraries vs. Boost.Test (and the > rest of Boost that we import). http://www.boost.org/doc/libs/1_37_0/libs/utility/throw_exception.html #define BOOST_NO_EXCEPTIONS > > Sample usage of Boost.Test: http://svn.boost.org/svn/boost/trunk/libs/test/example/unit_test_example_12.cpp > Note the code at the end setting up the test suite -- this is > boilerplate code that I think shouldn't...

2008/12/27 Mark Kromis <greybird at mac.com> > Just a curiosity question, why push for gtest vs Boost Test or > a different test suite? > I normally use Boost, and their test suite, so I'm more familiar with that. > So I was wondering is one better then the other, or is it just that someone > makes a patch for it? > I looked more into Boost.Test to see what's in

...exceptions, some with, and the results are > linked together. At the best case, it would complicate our build system to > be able to support different set of flags for building LLVM libraries vs. > Boost.Test (and the rest of Boost that we import). > > http://www.boost.org/doc/libs/1_37_0/libs/utility/throw_exception.html > #define BOOST_NO_EXCEPTIONS > Thanks for the pointer. > Sample usage of Boost.Test: > http://svn.boost.org/svn/boost/trunk/libs/test/example/unit_test_example_12.cpp > Note the code at the end setting up the test suite -- this is boilerplate >...

...ch? I have no experience with DocBook, but it seems that since it is XML-based it should also suffer from verbosity issues. For example, the Boost project, which originally used plain DocBook, decided to build a new ReST-like documentation format[1] on top of it. [1] http://www.boost.org/doc/libs/1_37_0/doc/html/quickbook.html

WikiFormatting for code documentation? :-) -scooter On Tue, Dec 9, 2008 at 7:56 AM, Mikhail Glushenkov <foldr at codedgers.com>wrote: > [Chris asked me to bring this up on the mailing list some time > ago, but I couldn't get to it. Sorry for that.] > > Since the beginning, I used ReST [1] for documenting llvmc, instead of > plain HTML that was used historically. In my

[Chris asked me to bring this up on the mailing list some time ago, but I couldn't get to it. Sorry for that.] Since the beginning, I used ReST [1] for documenting llvmc, instead of plain HTML that was used historically. In my opinion, ReST is much easier to write and read (in the text editor or on terminal); it can also be used to produce PDFs, man pages or HTML that looks exactly the same

Can you compare ReST to docbook? We've talked about using docbook for a long time. What are the pros and cons of each? Thanks, Tanya On Dec 9, 2008, at 7:56 AM, Mikhail Glushenkov wrote: > [Chris asked me to bring this up on the mailing list some time > ago, but I couldn't get to it. Sorry for that.] > > Since the beginning, I used ReST [1] for documenting llvmc, instead

...ptions, some with, and the results are > linked together. At the best case, it would complicate our build system to > be able to support different set of flags for building LLVM libraries vs. > Boost.Test (and the rest of Boost that we import). > > > http://www.boost.org/doc/libs/1_37_0/libs/utility/throw_exception.html > #define BOOST_NO_EXCEPTIONS > > > Sample usage of Boost.Test: > http://svn.boost.org/svn/boost/trunk/libs/test/example/unit_test_example_12.cpp > Note the code at the end setting up the test suite -- this is boilerplate > code that I think sh...

...t; with, and the results are linked together. At the best case, it >> would complicate our build system to be able to support different set >> of flags for building LLVM libraries vs. Boost.Test (and the rest of >> Boost that we import). > > http://www.boost.org/doc/libs/1_37_0/libs/utility/throw_exception.html > #define BOOST_NO_EXCEPTIONS > >> >> Sample usage of Boost.Test: >> http://svn.boost.org/svn/boost/trunk/libs/test/example/unit_test_example_12.cpp >> >> Note the code at the end setting up the test suite -- this is >>...