StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20750324
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-23T19:59:28.377
FavoriteCount
0
LastActivityDate
2013-12-23T20:13:23.227
LastEditDate
2013-12-23T20:13:23.227
LastEditorUserId
531122
OwnerUserId
531122
ParentId
20749394
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<p>It is always better to use error codes or exceptions. The choice between both depends on the implementation. I made a few example applications that explain in general what string errors, error codes and exceptions are.</p> <h2>String errors</h2> <p>This will work but it's ugly, also you don't know what errors there are defined without disecting the <code>GenerateError()</code> function).</p> <pre><code>#include <string> #include <iostream> class Example { public: std::string GenerateError(bool error) { if (error) { return "ERROR"; } return "OK"; }; }; int main() { Example example; if ("ERROR" == example.GenerateError(true)) { return 1; // failure } return 0; // success } </code></pre> <h2>Error Codes</h2> <p>With an <code>enum</code> you specify which error codes are available (in this case <code>Ok</code>, <code>Error</code> and <code>Error2</code>). This makes the code easier to understand and it will save you from mistakes. With enums you can also make use of <code>switch</code>.</p> <pre><code>#include <string> #include <iostream> enum ErrorCodes { Ok = 0, Error, Error2 //... }; class Example { public: ErrorCodes GenerateError(bool error) { if (error) { return ErrorCodes::Error; } return ErrorCodes::Ok; }; }; int main() { Example example; // Regular if statement if (ErrorCodes::Ok == example.GenerateError(true)) { return 1; // failure } else { return 0; // success } // switch statement switch (example.GenerateError(true)) { case Error: case Error2: return 1; // failure break; case Ok: return 0; // success break; } return 0; } </code></pre> <h2>Exceptions</h2> <p>Exceptions are a bit more complex but are definitely worth it to check out. Use exceptions when you want to obligate the user of the function to do something with the error. When the function does not require an action on an error it's probably better to use error codes.</p> <pre><code>#include <string> #include <iostream> class CustomException :public std::exception{ public: CustomException(const std::string m) :strMessage(m){} ~CustomException(void); const char* what(){ return strMessage.c_str(); } private: std::string strMessage; }; class Example { public: void GenerateError(bool error) { if (error) { throw CustomException("Critical error"); } return; }; }; int main() { Example example; try { example.GenerateError(true); } catch (CustomException ce) { std::cerr << ce.what() << std::endl; return 1; // failure } return 0; // success } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIs it acceptable to assign a "Read from file" function to a variable?
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSteve Van Opstal
UserOwnerUserId
1. USSteve Van Opstal
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POIs it acceptable to assign a "Read from file" function to a variable?
  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
  VTUpMod
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTAcceptedByOriginator
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.