StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17343920
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-27T13:02:43.183
FavoriteCount
0
LastActivityDate
2013-06-27T13:02:43.183
LastEditDate
LastEditorUserId
0
OwnerUserId
2527496
ParentId
17343308
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Each time you call fgetc() you advance the internal file pointer one character further. At the end of your while() loop the file pointer will then be at the end of the file. Subsequent calls intented to read on the file handle will fail with an EOF condition. The fgets manual says that : <blockquote> <blockquote> If the end-of-file is encountered while attempting to read a character, the eof indicator is set (feof). If this happens before any characters could be read, the pointer returned is a null pointer (and the contents of str remain unchanged). </blockquote> </blockquote> The consequence is that tmp_str is left unchanged. The garbage you get back when you call printf is actually a part of the conc() function stack. A solution to your problem would be rewinding the file pointer with fseek() just before calling fgets(). <pre><code>fseek(source, 0, SEEK_SET); </code></pre> Then a better way to get the size of your file would be to fseek to the end of the file, and use ftell to get the current position : <pre><code>long size; fseek(source, 0, SEEK_END); size = ftell(source); </code></pre> This being said, your code still has a problem. When you allocate on the stack (variables local to a function) you have to tell the size of the variable at compile time. Here your compiler allocates a char array of length 0. I suggest you investigate dynamic allocation with malloc of the keyword new if you're coding in C++. A proper allocation would look like this : <pre><code>char *tmp_str = malloc(size); // Here you read the file free(tmp_str); </code></pre> An simpler solution could be to preallocate a string large enough to hold your file. <pre><code>char tmp_str[1024 * 100]; // 100Kb </code></pre> Then use the size variable we got earlier to check the file will fit in tmp_str before reading.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POgetting string from file
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USthibauts
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
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.