StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2880136
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
27
CommunityOwnedDate
CreationDate
2010-05-21T07:01:28.573
FavoriteCount
0
LastActivityDate
2012-10-11T13:20:10.270
LastEditDate
2017-05-23T12:34:45.273
LastEditorUserId
-1
OwnerUserId
140719
ParentId
2879555
PostTypeId
2
Score
81
ViewCount
0
LastEditorDisplayName
text
Body
Alex has given you <a href="https://stackoverflow.com/questions/2879555/c-stl-how-to-write-wrappers-for-cout-cerr-cin-and-endl/2879561#2879561">an answer</a> how to syntactically solve that problem. However, I want to point out two other arguments regarding this issue: <ol> <li>No matter whether you're employing a using directive (<code>using namespace std</code>) or its lesser evil sister, a using declaration (<code>using std::cout</code>), overloading might lead to nasty surprises. It's not much hassle to type <code>std::</code> compared to spending half a night debugging to find out <a href="https://stackoverflow.com/questions/2712076/how-to-use-iterator-in-c/2712125#2712125">your code called <code>std::distance()</code> instead of your own <code>distance()</code> function</a>, just because you made a small mistake and <code>std::distance()</code> accidentally is a better match. </li> <li>A line of code gets written once, but - depending on its lifetime - it is read tens, hundreds, and some even thousands of times. So the time it takes to write a line of code simply doesn't matter at all, important is only the time it takes to read and interpret a line of code. Even if it takes three times as long to write a line with all the proper <code>std::</code> in place, if it makes reading it only 10% faster, it is still worth the trouble. So the important question is: Is it easier to read and interpret a line of code with all the <code>std::</code> in place or is it harder? From <a href="https://stackoverflow.com/questions/1452721/why-is-using-namespace-std-considered-a-bad-practice-in-c/1453605#1453605">another answer</a>: <blockquote> Here's one more data point: Many, many years ago, I also used to find it annoying having to prefix everything from the standard library with <code>std::</code>. Then I worked in a project where it was decided at the start that both <code>using</code> directives and declarations are banned except for function scopes. Guess what? It took most of us very few weeks to get to used to write the prefix and after a few more weeks most of us even agreed that it actually made the code more readable. (There's a reason for that: Whether you like shorter or longer prose is subjective, but the prefixes objectively add clarity to the code. Not only the compiler, but you, too, find it easier to see which identifier is referred to.) In a decade, that project grew to have several million lines of code. Since these discussions come up again and again, I once was curious how often the (allowed) function-scope <code>using</code> actually was used in the project. I grep'd the sources for it and only found one or two dozen places where it was used. To me this indicates that, once tried, developers didn't find <code>std::</code> painful enough to employ using directives even once every 100kLoC even where it was allowed to be used. </blockquote> I think it's sad that every book and tutorial you'll find skips <code>std::</code>, because that makes people getting used to read the code that way. When I taught C++ for several years (after the above mentioned experience), I told my students that I don't want to see any <code>using</code> directive or declaration in their code. (The only exception to that rule is <code>using std::swap</code>, BTW, which you'll need in order to have <code>swap(a,b)</code> pick up overloads outside of namespace <code>std</code>.) Once they got used to it, they didn't mind and, when asked about it, they said they find code without the <code>std::</code> prefix confusing. Some even added the <code>std::</code> prefix to code they typed from a book or tutorial which didn't have it. </li> </ol> Bottom line: What's so hard about typing <code>std::</code> that everybody gets so worked up about it? By now I have been doing it for >15 years, and I don't miss <code>using</code> at all. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC++ Standard Library: How to write wrappers for cout, cerr, cin and endl?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USsbi
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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

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.