Talk:C syntax/Archive 2
This is an archive of past discussions about C syntax. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 1 | Archive 2 |
Is this really about C syntax?
This article covers much more than syntax. It talks about type and array semantics, even including the detail that strings are null-terminated! None of that is syntax. Should the semantic content be removed? or should the title and lead be changed?
Also, this article talks about C as though it has been the same from the beginning to the present. The original C in which the original Unix was written had many differences from current C. --Macrakis (talk) 14:45, 28 June 2017 (UTC)
- I suppose it would be possible, for example, to describe the syntax of C strings with a series of rules. However, it is a lot easier and better to describe what a string is in C because most of the rules follow from understanding that. Johnuniq (talk) 03:36, 29 June 2017 (UTC)
- I am not sure what you mean. The syntax of C string literals is part of the syntax of the language. The semantics of strings at run-time, e.g., that they are null-terminated, is not part of the syntax of the language at all. --Macrakis (talk) 20:29, 30 June 2017 (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)
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? — Preceding unsigned comment added by Friendly person (talk • contribs) 01:56, 13 October 2018 (UTC)
A Commons file used on this page or its Wikidata item has been nominated for speedy deletion
The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for speedy deletion:
You can see the reason for deletion at the file description page linked above. —Community Tech bot (talk) 19:09, 18 August 2022 (UTC)