Thread: Syntax wars

Ok, I have posted a couple of very small programs(I am totally new to C)and it seems that I will ask a question and people will answer it just fine(thanks guys )but then I also get like 5 other people telling me that I should not use 'goto' or I should use 'fgets' instead of 'gets'. I get what they are saying, like this line will be less confusing and such but there seems to be a long list so my question is, does anyone know of a website, have a list, or know of a book that has a list, of at least the common do's and don'ts for syntax, like something that shows you which is better in which situation and why and so, if you do please tell me.

Prelude's sig has an excelent link that should be in everyones bookmarks,

http://www.eskimo.com/~scs/C-faq/top.html

Originally posted by CAP
Ok, I have posted a couple of very small programs(I am totally new to C)and it seems that I will ask a question and people will answer it just fine(thanks guys )but then I also get like 5 other people telling me that I should not use 'goto' or I should use 'fgets' instead of 'gets'. I get what they are saying, like this line will be less confusing and such but there seems to be a long list so my question is, does anyone know of a website, have a list, or know of a book that has a list, of at least the common do's and don'ts for syntax, like something that shows you which is better in which situation and why and so, if you do please tell me.

Don't be put off about people pointing out problems with your code that don't relate to your original question. I always try and highlight any problem (or potential one) that I see.

I won't lecture on gets() and goto in this thread, I'll only say that if you've got a book which you're learning from, and it starts with promoting these two statements, junk it, and get a better one.

I look at this way; the advice others give is always worth looking into. Some of the replies I've gotten to my various questions have made me think more about which method would make more sense to use, and how to better attack any problems that might arise.

Programming is a difficult practice and you can't learn the nuances from books or websites most of the time. I've found that when I'm doing something wrong, I don't find out about it until someone more knowledgeable points it out, which is a very good reason to hang around programmers better than you are. It's highly recommended that you even offer up what you consider to be working code for double checking so that your mistakes don't go unchecked. But beware of bad or unfounded advice, not everyone who thinks they know something actually do. You should always ask a lot of questions until you are satisfied that the advice was sound and you understand why.

-Prelude

Thanks a lot and believe me I have no problems whatsoever with people giving advice or critism(including on spelling ). I enjoy looking at posts that not only tell me what I have done wrong and answer my questions, but will give me helpful hints so thanks to all of you people who post answers that are helpful and helping out beginners like me .

I've found that when I'm doing something wrong, I don't find out about it until someone more knowledgeable points it out, which is a very good reason to hang around programmers better than you are. It's highly recommended that you even offer up what you consider to be working code for double checking so that your mistakes don't go unchecked.

Precisely.

Going on from that whole "sticking around better programmers than you are thing" from above, why else would I be here every day?

Originally posted by pinko_liberal
A paper some of you might find interesting to read
http://pplab.snu.ac.kr/courses/PL200...p261-knuth.pdf

Great! Does anyone know where I can download a Utopia84 Compiler from?

foffo spearjig


PS For the non-English of you, the above is meant to be gently ironic ( and I don't mean in the Alanis Morrissette way )