StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POc++ code cons/pros
primarykey
Id
2496138
data
AcceptedAnswerId
2496155
AnswerCount
5
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-03-22T22:09:28.270
FavoriteCount
0
LastActivityDate
2010-03-23T00:07:25.713
LastEditDate
2010-03-23T00:06:55.387
LastEditorUserId
230075
OwnerUserId
230075
ParentId
0
PostTypeId
1
Score
0
ViewCount
343
LastEditorDisplayName
text
Body
below i have a code that runs in most of my simple programs .. . i want to know if it's good/bad ... and cons/pros . . win32 header file: win32.h <pre><code>// example of a not realated code to exaplin the question // this header have all win32 includes like win/proces/stdarg/string ... etc #include <windows.h> #include <process.h> #include <stdarg.h> </code></pre> main header file: inc.h <pre><code>//this file includes the following //top : the windows header file #include "win32.h" // include the win32.h header file //the extern define which is the question //the first include cause the INCS to be defined //any include afterwards causes the DD to go from 'nothing' into 'extern' #ifndef INCS #define INCS #define DD #else #define DD extern #endif // unrealted code to be more informative //middle area of the file have the variables /defines or w/e #ifndef VARS #define titlen L"my program" #endif DD wchar_t gtitle[512]; DD wchar_t gclass[512]; DD wchar_t gdir[32767]; //last area of the file // this bottom area have the project's files' all included all headers and code #include "resources.h" #include "commonfunctions.cpp" </code></pre> then all files have something like this commonfunctions.cpp <pre><code>//a code just to be more informative and it's not realted to the question #include "inc.h" // no need for includings ? DD inline bool icmp( const char *String1, const char *String2 ) { if ( _stricmp( String1, String2 ) == 0 ) { return true; } return false; } DD inline bool scmp( const char *String1, const char *String2 ) { if ( strcmp( String1, String2 ) == 0 ) { return true; } return false; } </code></pre> <hr> <h2>DD refers to the #define DD extern</h2> all global variables have DD infront of them and all functions/subs have DD too, that will cause the functions to be defined as extern in all file when included for the second time is there a bad side of this ? . i came up with this idea and it wasn't problematic at all in small programs . but before i apply it in a large project will it be problematic ?. . . <h1>Now to the Question</h1> DD here means the #define DD extern DD will remove the need to do a psudo outside the code or in headers DD will remove the need to define extern variables in each page DD will remove the need to do the #includes of each header in each file Now will this DD that is demostrated in the code upthere be a problem in a bigger code ? edit: i edited the question to be more clear thanks in advance. 
Tags
<c++>
Title
c++ code cons/pros
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USVirusEcks
UserOwnerUserId
1. USVirusEcks
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
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.