StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11379183
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-07-07T22:31:38.967
FavoriteCount
0
LastActivityDate
2012-07-07T22:31:38.967
LastEditDate
LastEditorUserId
0
OwnerUserId
827263
ParentId
11379088
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
There are several problems with your code. <code>int main()</code> should be <code>int main(void)</code>; this is a minor issue that almost certainly won't hurt anything, but the latter is more correct. You don't check whether the <code>fopen()</code> calls succeed. You're using <code>i</code> to count the characters you read, but you never do anything with its value. The <code>getc()</code> function returns a result of type <code>int</code>, so you should definitely make <code>tempChar</code> an <code>int</code>. The reason for this is that it can return either a valid character value (which will fit in a <code>char</code> object) or the value <code>EOF</code> which is typically <code>-1</code>. By storing the result of <code>getc()</code> in a <code>char</code> object, either you'll never see <code>EOF</code> (if plain <code>char</code> is unsigned), or you won't be able to distinguish <code>EOF</code> from a valid input character. In a comment on Razvan's answer, you said you changed the test to <code>tempChar != EOF</code>. Apart from the problem I explained above, on the first iteration of the loop <code>tempChar</code> has not been initialized, and the result of the comparison is unpredictable. The conventional way to write an input loop using <code>getc()</code> is: <pre><code>int c; while ((c = getc(f)) != EOF) { /* do something with c */ } </code></pre> As a matter of style, <code>write</code> is not a very good name for a <code>FILE*</code>. For one thing, there's a function of that name (defined by POSIX, not by C, but it's still potentially confusing). You might call the <code>FILE*</code> objects <code>in</code> and <code>out</code> instead.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUnknown Logical Error Using the getc() Function in C
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USKeith Thompson
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUnknown Logical Error Using the getc() Function in C
 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
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.