well if you want to do it the hard way.. your warning means that basically your code is ligned up properly. check all your lines, you prolly have a comma missing or you forgot a " somwewhere.
well if you want to do it the hard way.. your warning means that basically your code is ligned up properly. check all your lines, you prolly have a comma missing or you forgot a " somwewhere.
Warning: Opinions subject to change without notice
The C Library Reference Guide
Understand the fundamentals
Then have some more fun
I was able to figure out what the problem was. I had a line that I needed a " in. I fixed it and the program compiled fine.Originally Posted by caroundw5h
good stuff. next time, just copy and paste EXACTLY.
Warning: Opinions subject to change without notice
The C Library Reference Guide
Understand the fundamentals
Then have some more fun
Yeah because nothing helps you learn better than a good old "copy and paste" job.
Quzah.
Hope is the first step on the road to disappointment.
stop it, now you know that wasn't what I meant.Yeah because nothing helps you learn better than a good old "copy and paste" job.
Quzah.
Warning: Opinions subject to change without notice
The C Library Reference Guide
Understand the fundamentals
Then have some more fun
Sure it is. Some one thought it would be "helpful" to post a full working version, and you told them to copy and paste it.
Quzah.
Hope is the first step on the road to disappointment.
although this won't really get us anywhere, i'll bite. I wasn't condoning the copy and paste action, merely helping along to doing it properly. If the OP chose to copy and paste rather than think it through...so be it.
i've bitten.
Warning: Opinions subject to change without notice
The C Library Reference Guide
Understand the fundamentals
Then have some more fun
I tried to help as much as possible. While posting the full code, I did take my time to explain what each line and function did, and how it worked.
Though, I did not make myself clear in my first attempt of helping the OP, which sent him off to write a code that wouldn't compile. I decided to correct my mistakes and help him learn about a peice of code that works "in most compilers". Some people learn best by visualizing.
I'm sorry for any inconvenience.
Segmentation Fault: I am an error in which a running program attempts to access memory not allocated to it and core dumps with a segmentation violation error. This is often caused by improper usage of pointers, attempts to access a non-existent or read-only physical memory address, re-use of memory if freed within the same scope, de-referencing a null pointer, or (in C) inadvertently using a non-pointer variable as a pointer.
It doesn't inconvenience me. It annoys me. It annoys me when people ignore the forum guidelines and simply do everything for people, which they're not supposed to ask for. It doesn't matter though, because even if you stop doing it, a hundred more people will still do it.
So again, it isn't an inconvenience. It's an annoyance.
Quzah.
Hope is the first step on the road to disappointment.
