Talk:C syntax

C/C++ C‑class Low‑importance

	This article is within the scope of WikiProject C/C++, a collaborative effort to improve the coverage of C and C++ topics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.C/C++Wikipedia:WikiProject C/C++Template:WikiProject C/C++C/C++
C	This article has been rated as C-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the importance scale.

Computing: Software C‑class Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
C	This article has been rated as C-class on Wikipedia's content assessment scale.
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Mid-importance).

Template:IEP assignment Template:Findsourcesnotice

Archives

Archive 1

Archive 2

This page has archives. Sections older than 100 days may be automatically archived by when more than 4 sections are present.

Evaluation order

The last paragraph 'Evaluation order and Lazy evaluation' is almost completely wrong! Its author should read comp.lang.c FAQ list section 3, especially answer to question 3.5. Constructions like a != NULL && func(a++) do NOT invoke undefined behaviour. The writer is confusing C's short circuit evaluation to lazy evaluation which is a completely different thing. --193.143.83.252 17:36, 26 Mar 2004 (UTC)

Agree completely. That section was completely incorrect. I tried to fix it. Kevin Saff 14:16, 7 Apr 2004 (UTC)

Your version is much better than the original! I just added one sequence point to the list. 193.143.83.252

vfd

This article was proposed for deletion January 2005. The discussion is archived at Wikipedia:Votes for deletion/C syntax. Joyous 22:46, Jan 22, 2005 (UTC)

Standard library != C Syntax

The standard library (for which none of the header file names have been provided I might add) has nothing to do with the syntax of C. C can be used with other libraries or none at all; its syntax is independent of them. The translation of command-line arguments is the job of the linker and again has nothing to do with C syntax.

And then I find myself guilty of the same offense, so take what I said with a grain of salt.—Kbolino 05:41, Apr 6, 2005 (UTC)

Function pointer example - why include parameters for command line parsing with no command line parsing needed?

This seems like a small pet peeve, but why include the arguments for command line argument parsing (int argc, char* args[]) in the main function of an example, like the function pointer example, where the said example doesn't use them? — Preceding unsigned comment added by Travelsonic (talk • contribs) 20:18, 20 September 2017 (UTC)[reply]

For Loop explanation

The explanation of the syntax of for (;;) is weak. I was following nicely until suddenly here's this "continue;" thing. The problem I think is in trying to equate the for construct to a while construct. Just explain the for construct! What I came here wanting to know was

1. where does e1 happen (at the beginning, right)

2. where does e2 happen? at the top or at the bottom of the loop? and how exactly does it work? it's a boolean expression. In c, a zero is "true" anything else is "false". If e2 evaluates as true, does the loop stop or go around again?

3. where does e3 happen?