Loading .txt Files

FILE *File; long Size; char *text; File = fopen(FileName, "r"); fseek(File, 0, SEEK_END); Size = ftell(File); rewind(File); text = (char *)malloc(Size+1); fread(text, 1, Size, File); text[Size] = ''\0''; SetWindowText(hEdit, text); fclose(File); free(text);

[Resist Windows XP''s Invasive Production Activation Technology!]

Thanks a lot, I was trying to figure that out for about 3 days.

dude, get away from C, get on the C++ bandwagon.
I thought for awhile that I should learn C before C++, but then I got really pissed at the terrible pointers deal with C and switched.
Code to read in from a file in C++ is almost identical to code to read in from the keyboard:

#include <iostream.h>
#include <fstream.h>

int main(void)
{
ifstream fin("data.txt");
int x;
cout<<"read in from keyboard"<<endl;
cin>>x;
cout<<"read in from file"<<endl;
fin>>x;
fin.close();

return 0;
}


see how easy!!! No dealing with pointers!!! No learning new functions!!! It's so easy!!! This is why I switched right here!!!

Edited by - capn_midnight on January 7, 2002 12:56:06 PM

But you''ll have to realize that in game programming you''ll be using pointers fairly often.

But I agree. C++ is nicer.

ok then, new question....

using c++ is nicer, but is it reliable enough for game save files that load in a lot of numbers, strings and other things?

just wondering, i like the c++ way, but every example or tut i see shows c examples.

quote:

---

Original post by Anonymous Poster
Same thing in c (notice, no pointers either):

---

#include <stdio.h> #include <conio.h> int main(void) { FILE *in = fopen("data.txt","r"); int x; printf("read in from keyboard\n"); x=getch(); printf("read in from file\n"); x = getc(in); fclose(in); }

Sorry to be a nit picker, but what do you call FILE *in? It sure looks like a pointer to me.

Sorry to be a nit picker, but what do you call FILE *in? It sure looks like a pointer to myou cant count that! this pointer is sooooo simple to use!

Well, C is easier to understand for someone new, specially if you are explaining an algorithm.

I think its easier to teach how to write file I/O functions first, and then when that part is understood, teach how to implement a file I/O Class.