StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20863348
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-12-31T21:24:45.400
FavoriteCount
0
LastActivityDate
2013-12-31T21:24:45.400
LastEditDate
LastEditorUserId
0
OwnerUserId
1774667
ParentId
20862985
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Here is an attempt at an RAII class that does something similar: <pre><code>template<std::size_t N> class StringGetter_N { private: std::unique_ptr<char[]> buffer; public: StringGetter_N() { buffer.reset( new char[N] ); buffer.get()[0] = 0; } explicit StringGetter_N(char const* name) { buffer.reset( new char[N] ); strcpy_s(buffer.get(), N-1, name); buffer.get()[N-1] = 0; // always null terminate } StringGetter_N( StringGetter_N&& other ) = default; char* GetString() { return buffer.get(); } }; class StringGetter : StringGetter_N<1024> { explicit StringGetter( const char* name ):StringGetter_N<1024>(name) {} StringGetter():StringGetter_N<1024>() {} }; </code></pre> notice that I delegated the resource management to a smart pointer. Single responsibility principle means that the resource management object (like a smart pointer) can do just that, and if you want to write a class that represents a heap-allocated buffer of fixed size, you delegate that sub problem to the smart pointer, and just manage it in your class. As it happens, <code>std::unique_ptr</code> properly implements But really, it is usually much simpler to just use a <code>std::vector</code>, as you can usually determine how much space you need at run-time before needing a buffer to write to. If you do implement your own RAII class, you should follow these rules: <ul> <li>Single argument constructors that are not copy/move constructors should usually be <code>explicit</code>.</li> <li>If you implement a non-trivial destructor, you must (implement or block usage of) (copy and/or move constructor) and (copy and/or move operator=). This is known as the rule of 3 (or rule of 5 in C++11).</li> <li>Your RAII class should do little except manage the resource. If you want to do something else, use an RAII class to manage the resource, then store it within another class that does the fancy extra work.</li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC++ RAII - Do I have this right?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USYakk - Adam Nevraumont
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. This table or related slice is empty.
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.