StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
687302
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-03-26T19:51:02.063
FavoriteCount
0
LastActivityDate
2009-03-28T03:16:28.130
LastEditDate
2009-03-28T03:16:28.130
LastEditorUserId
10559
OwnerUserId
10559
ParentId
193471
PostTypeId
2
Score
15
ViewCount
0
LastEditorDisplayName
jwfearn
text
Body
[Answering my own question] It depends. This is an apples to oranges comparison. Although similar, these macros are NOT interchangeable. Here's a summary of how each works: <code>BOOST_STATIC_ASSERT( P )</code> generates a compilation error if <code>P != true</code>. <code>BOOST_MPL_ASSERT(( P ))</code> generates a compilation error if <code>P::type::value != true</code>. The latter form, despite requiring double parentheses, is especially useful because it can generate more informative error messages if one uses Boolean nullary Metafunctions from Boost.MPL or TR1's <code><type_traits></code> as predicates. Here is an example program that demonstrates how to use (and misuse) these macros: <pre><code>#include <boost/static_assert.hpp> #include <boost/mpl/assert.hpp> #include <type_traits> using namespace ::boost::mpl; using namespace ::std::tr1; struct A {}; struct Z {}; int main() { // boolean predicates BOOST_STATIC_ASSERT( true ); // OK BOOST_STATIC_ASSERT( false ); // assert // BOOST_MPL_ASSERT( false ); // syntax error! // BOOST_MPL_ASSERT(( false )); // syntax error! BOOST_MPL_ASSERT(( bool_< true > )); // OK BOOST_MPL_ASSERT(( bool_< false > )); // assert // metafunction predicates BOOST_STATIC_ASSERT(( is_same< A, A >::type::value ));// OK BOOST_STATIC_ASSERT(( is_same< A, Z >::type::value ));// assert, line 19 BOOST_MPL_ASSERT(( is_same< A, A > )); // OK BOOST_MPL_ASSERT(( is_same< A, Z > )); // assert, line 21 return 0; } </code></pre> For comparison, here are the error messages my compiler (Microsoft Visual C++ 2008) generated for lines 19 and 21 above: <pre><code>1>static_assert.cpp(19) : error C2027: use of undefined type 'boost::STATIC_ASSERTION_FAILURE<x>' 1> with 1> [ 1> x=false 1> ] 1>static_assert.cpp(21) : error C2664: 'boost::mpl::assertion_failed' : cannot convert parameter 1 from 'boost::mpl::failed ************std::tr1::is_same<_Ty1,_Ty2>::* ***********' to 'boost::mpl::assert<false>::type' 1> with 1> [ 1> _Ty1=A, 1> _Ty2=Z 1> ] 1> No constructor could take the source type, or constructor overload resolution was ambiguous </code></pre> So if you're using metafunctions (as defined <a href="http://www.boost.org/doc/libs/1_38_0/libs/mpl/doc/refmanual/metafunction.html" rel="noreferrer">here</a>) as predicates then <code>BOOST_MPL_ASSERT</code> is both less verbose to code and more informative when it asserts. For simple boolean predicates, <code>BOOST_STATIC_ASSERT</code> is less verbose to code although its error messages may be less clear (depending on your compiler.)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhich is better BOOST_MPL_ASSERT or BOOST_STATIC_ASSERT?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USjwfearn
UserOwnerUserId
1. USjwfearn
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhich is better BOOST_MPL_ASSERT or BOOST_STATIC_ASSERT?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.