Help? New to C and getting trouble.

Quote:

---

Perhaps your CMD window is flashing up and going away too fast for you to see it.

---

Yeah, that's what Elysia's solution is getting at. I do not quite understand if RahulDhanpat is having problems figuring out how to run the program, or having problems seeing the output of the program when run.

Quote:

---

Common ways are add "getch()" at the end of of main.

---

getch() is non-standard though, I believe getchar() is what should be used for C.

Quote:

---

And if you can, I do suggest you try Visual Studio 2008 Express. VC6 is old, and age is making it bad.

---

I agree, and I note that it is available at zero price.

EDIT:

Quote:

---

Even using PCH, it will still compile fine with other compilers.

---

Not with a #include "stdafx.h". So the OP either ends up either adding the line everytime he/she gets an example to learn from, or simply disables the feature until he/she actually wants to use it.

Dear freinds.. I m very new to seee.. just started C three days back... i understand that i m just wasting your all time... I wont take alot of time now. Please suggest me something which can help meto learn C and reach the place where you all are now? and how can i do it more effeciently? Its difficult for me to pay and learn so i can;t join any institute so i have taken step to learn it my self as chellange and i hope i will get enough help from this forum to learn C .

I hope No one critise me. :)

Quote:

---

Originally Posted by laserlight

getch() is non-standard though, I believe getchar() is what should be used for C.

---

Ah, getchar() is the standard one.

Quote:

---

Not with a #include "stdafx.h". So the OP either ends up either adding the line everytime he/she gets an example to learn from, or simply disables the feature until he/she actually wants to use it.

---

Sure it compiles. It's just a header, that's all. PCH just makes compiling the header faster.
And in any case, you shouldn't just copy and replace all code when using examples. You can just replace all code below the stdafx.h line if you want.
Or you can stuff all the headers inside stdafx.h and never have to worry about including the headers in examples and code all over the place.

Of course, when writing real applications, you're better off including only headers you need, but for examples and such, I think you can get away with doing that. It's what I typically do.

And as for learning, the best start is get a book, read tutorials, try examples and ask questions.
You can also ponder if you want to use either C or C++. C++ can be more high level than C and thus easier, but it's a deeper language with much more functionality.

Quote:

---

Sure it compiles. It's just a header, that's all.

---

Eh, but if "stdafx.h" is not available, the code will not compile. On the other hand, on a vanilla compiler setup without PCH enabled, my code example will compile, and in fact is pretty much guaranteed to do so.

Quote:

---

PCH just makes compiling the header faster.

---

Indeed, thus it is unnecessary.

Quote:

---

And in any case, you shouldn't just copy and replace all code when using examples. You can just replace all code below the stdafx.h line if you want.

---

That's true.

Quote:

---

Or you can stuff all the headers inside stdafx.h and never have to worry about including the headers in examples and code all over the place.

---

That's poor practice when learning C or C++ since one does not know what headers are actually needed.

Quote:

---

Of course, when writing real applications, you're better off including only headers you need, but for examples and such, I think you can get away with doing that. It's what I typically do.

---

... consequently, one never actually learns what headers are needed until it is time to write a real application.

Quote:

---

Originally Posted by laserlight

Eh, but if "stdafx.h" is not available, the code will not compile. On the other hand, on a vanilla compiler setup without PCH enabled, my code example will compile, and in fact is pretty much guaranteed to do so.

---

But if PCH is enabled, stdafx.h will exist, so the point is moot.

Quote:

---

Indeed, thus it is unnecessary.

---

It's a convenience.

Quote:

---

That's poor practice when learning C or C++ since one does not know what headers are actually needed.

---

But then again, such things are noted in the docs and consequently, tutorials typically include the right headers too, don't they?

Quote:

---

But if PCH is enabled, stdafx.h will exist, so the point is moot.

---

Not all compilers use "stdafx.h" for precompiled headers. In fact, I think only one family of compilers does so.

Quote:

---

But then again, such things are noted in the docs and consequently, tutorials typically include the right headers too, don't they?

---

Typically, but not always. Besides, it is better to learn from one's mistakes than develop bad habits.

To the OP:

http://www.cprogramming.com/tutorial.html

Quote:

---

Originally Posted by laserlight

Not all compilers use "stdafx.h" for precompiled headers. In fact, I think only one family of compilers does so.

---

But the point being, whether or not it uses stdafx.h as PCH, it compiles on other projects even if you use PCH, because all you do is include stdafx.h and the file is created when PCH is enabled.
We can argue all we want about that, but the main point of discussion of PCH is whether it's worth using or not for newbies. They have to add an extra line to the source files and gain little from it, or so most say.
But then again, it doesn't hurt to have that line there.

Quote:

---

Typically, but not always. Besides, it is better to learn from one's mistakes than develop bad habits.

---

Well, I'll agree with you on that. Being a newbie, you don't need to add things to PCH files.

Quote:

---

But the point being, whether or not it uses stdafx.h as PCH, it compiles on other projects even if you use PCH, because all you do is include stdafx.h and the file is created when PCH is enabled.

---

That's fine if it were a real application. Not so when one is asking for help to solve a problem.

Quote:

---

We can argue all we want about that, but the main point of discussion of PCH is whether it's worth using or not for newbies. They have to add an extra line to the source files and gain little from it, or so most say.

---

Indeed. However, I can state very clearly that this is non-standard and not needed here.

Quote:

---

But then again, it doesn't hurt to have that line there.

---

It hurts the philosophy of getting newbies (or anyone else) to post the smallest and simplest (compilable) program that demonstrates the problem.

I'm having a feeling this discussion will spiral on forever, so I think I'm going to stop feeding the discussion here and get back to the topic at hand.

Quote:

---

I'm having a feeling this discussion will spiral on forever, so I think I'm going to stop feeding the discussion here and get back to the topic at hand.

---

*sigh*
It seems that we have another topic of contention besides indentation style :p

Quote:

---

Originally Posted by RahulDhanpat

I hope No one critise me. :)

---

Oh I hope we DO criticize you - but I hope you know we're not criticizing YOU personally. It's very helpful if you can set your personal self, aside, and try to understand what you can when you're being corrected/shown something.

As far as learning, there are some good C tutorials on-line. This forum has a FAQ that is well done, also. Google for "C language tutorial", and follow the links. Some are quite excellent.

And welcome to the C programming forum, RD! :)

You all are so expert that even i dont understand your technical things. How the hell you all know this much???????????????????

I m really very impressed !!!! Specially Elysia ..

We've been programming for years (most of us anyway, I believe), so experience keeps stacking up!