#include 
int main()
{
    FILE *in;
    int key;
    if ((in = fopen("junk.txt", "r")) == NULL)
    {
        puts("Unable to open the file");
        return 0;
    }
    while (!feof(in))
    {
        key = fgetc(in);
        if (!feof(in))
            putchar(key);
    }
    fclose(in);
    return 0;
}

Originally posted by windwaker

---

#include 
int main()
{
    FILE *in;
    int key;
    if ((in = fopen("junk.txt", "r")) == NULL)
    {
        puts("Unable to open the file");
        return 0;
    }
    while (!feof(in))
    {
        key = fgetc(in);
        if (!feof(in))
            putchar(key);
    }
    fclose(in);
    return 0;
}

I didn't write the main code for this, though I did mess around with it a bit, and created junk.txt, though every time I compile it with MinGW, it crashes.

---

in = fopen("junk.txt", "r");

if(!in)
{
     puts("Couldn't open! Thou sucks!");
}

while ((key = fgetc(in)) != EOF)
{
putchar(key);
}

#include <stdio.h>

int main()
{

    FILE *in;
    FILE *dude;

    int key;
	in = fopen("junk.txt", "r");
	if (!in)
    {
        puts("Unable to open the filez");
        return 0;
    }
	while ((key = fgetc(in)) != EOF)
	{
	putchar(key);
	}
    fclose(in);
    return 0;
}

Originally posted by windwaker

---

Edit: Yesssss... evidently, it wasn't looking for the file in that directory, junk.txt, it was looking for C:\junk.txt. Is there any way to tell it to look for junk.txt in it's own directory?

---

Originally posted by X-Grade

---

Bleh! Why use old C functions when newer C++ functions are much faster.

---

Originally posted by Disch

---

Originally posted by X-Grade

---

Bleh! Why use old C functions when newer C++ functions are much faster.

---

How do you figure?

Besides... perhaps he's coding in C and not C++? ;P

I'm a C/C++ hybrid guy myself -- but I still prefer to use stdio.h for file i/o. Much cleaner/simpler more straightforward. Some C++ additions are good... some are just downright silly (like iostreams)

---

Originally posted by X-Grade

---

As a quick and simple exemple, when using printf, the application analyse the format during runtime, while cout analyse the format during compilation time (It also greatly reduce the risk of errors). Also, iostream use a "uniform" syntax. You can, for exemple, take the above code, change one type, add one line, and you're application writes to a buffer before writting everything to the console. A really appreciated functionality when working on huge mainframe.

---