StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13694703
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-12-04T01:24:57.333
FavoriteCount
0
LastActivityDate
2012-12-04T01:42:24.433
LastEditDate
2012-12-04T01:42:24.433
LastEditorUserId
15168
OwnerUserId
15168
ParentId
13694605
PostTypeId
2
Score
24
ViewCount
0
LastEditorDisplayName
text
Body
For the maximum reliability: <ul> <li>Compile the C source with a C compiler.</li> <li>Compile the C++ source with a C++ compiler</li> <li>Preferably, write the main() function in C++.</li> <li>Link the program with a C++ compiler.</li> </ul> Make sure that the C headers are either themselves aware of C++ or that the C++ code includes the C headers inside an <code>extern "C" { ... }</code> block. Either (C header file <code>cheader.h</code>): <pre><code>#ifndef CHEADER_H_INCLUDED #define CHEADER_H_INCLUDED #ifdef __cplusplus extern "C" { #endif ...main contents of header... #ifdef __cplusplus } #endif #endif /* CHEADER_H_INCLUDED */ </code></pre> or (C++ source code): <pre><code>extern "C" { #include "cheader.h" } </code></pre> Modern C style is very close to the common subset of the C and C++ languages. However, arbitrary C code is not C++ code for any of a very large number of reasons, and simply calling the C source files C++ source files (by changing the extension, or simply by compiling with the C++ compiler) is not guaranteed to be successful. In general, it is easier to compile C as C and C++ as C++ and then link the resulting object files with the C++ compiler (to ensure the correct support libraries are invoked). However, if the MSVC compiler is saying that programs using MFC have to be written solely in C++ (MFC requires C++ compilation (use a .cpp suffix) is the reported error), then you may have no choice but to ensure that your C code is compilable as C++ code. That means you'll have to cast the return values from <code>malloc()</code> et al; you have to worry about other places where you do not use a cast to convert a <code>void *</code> into some other pointer type; you have to worry about <code>sizeof('a') == 4</code> in C and <code>sizeof('a') == 1</code> in C++; you have to ensure that every function is declared before it is used; you have to ensure your C code does not use any C++ keywords (<code>typename</code>, <code>class</code> in particular; also <code>inline</code> sometimes — but the complete list is quite large). In some circles, you'd have to worry about the use of features in C99 that are not in C++2003 or C++2011, such as flexible array members, designated initializers, compound literals, variable-length arrays, and so on. However, if the C code is for MSVC, then that probably isn't going to be a problem; those features are not supported by the MSVC C compiler (it only supports C89, not C99). FWIW: I have a script to hunt down C++ keywords. It contains the following comment: <pre><code># http://en.cppreference.com/w/cpp/keywords # plus JL annotations # and C (<iso646.h>) # and_eq C (<iso646.h>) # alignas (C++11 feature) # alignof (C++11 feature) # asm C (core) # auto(1) C (core) # bitand C (<iso646.h>) # bitor C (<iso646.h>) # bool C99 (<stdbool.h>) # break C (core) # case C (core) # catch # char C (core) # char16_t (C++11 feature) # char32_t (C++11 feature) # class # compl C (<iso646.h>) # const C (core) # constexpr (C++11 feature) # const_cast # continue C (core) # decltype (C++11 feature) # default(1) C (core) # delete(1) # double C (core) # dynamic_cast # else C (core) # enum C (core) # explicit # export # extern C (core) # false C99 (<stdbool.h>) # float C (core) # for C (core) # friend # goto C (core) # if C (core) # inline C (core) # int C (core) # long C (core) # mutable # namespace # new # noexcept (C++11 feature) # not C (<iso646.h>) # not_eq C (<iso646.h>) # nullptr (C++11 feature) # operator # or C (<iso646.h>) # or_eq C (<iso646.h>) # private # protected # public # register C (core) # reinterpret_cast # return C (core) # short C (core) # signed C (core) # sizeof C (core) # static C (core) # static_assert (C++11 feature) # static_cast # struct C (core) # switch C (core) # template # this # thread_local (C++11 feature) # throw # true C99 (<stdbool.h>) # try # typedef C (core) # typeid # typename # union C (core) # unsigned C (core) # using(1) # virtual # void C (core) # volatile C (core) # wchar_t C (core) # while C (core) # xor C (<iso646.h>) # xor_eq C (<iso646.h>) </code></pre> The <code>(1)</code> suffixes is a footnote at CPP Reference: <ul> <li><code>(1)</code> — meaning changed in C++11 </li> </ul>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to use C source files in a C++ project?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJonathan Leffler
UserOwnerUserId
1. USJonathan Leffler
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to use C source files in a C++ project?
 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
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CO" MFC requires C++ compilation (use a .cpp suffix) "
 singulars
 PostPostId
 PO
 UserUserId
 USAl2O3
2. COThen you can't use C after all because MS doesn't allow it. Tough. You'll have to make sure your C code is also C++ code. That's harder work than making your C code into C code. Have fun — or choose a different O/S. (I don't know whether that error message means you can't use the `extern "C"` notation or not; I've not coded with MSVC and MFC.) Note that if you had mentioned the platform in your question, you might have gotten better answers straight away — and I might not have tried answering at all.
 singulars
 PostPostId
 PO
 UserUserId
 USJonathan Leffler

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.