Talk:C (programming language)/Archive 17
 | This is an archive of past discussions about C (programming language). 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 10 | ← | Archive 15 | Archive 16 | Archive 17 |
Why are characters and booleans irelevant to C programming?
@Fbergo: Why are booleans and characters irelevant to C (programming language)? --Kreyren (talk) 11:40, 12 December 2019 (UTC)
- They are not irrelevant, and both are already mentioned in the first paragraph of the Data Types section. This article is already quite long for wikipedia (WP:TOOLONG), repeating information is not an improvement. Your tutorial-like sections on basic types only made the article less readable. The article should not be a language tutorial (WP:NOTTEXTBOOK). Fbergo (talk) 14:39, 12 December 2019 (UTC)
Assuming incorrect use of print formatted in an example
Based on https://en.wikipedia.org/wiki/Talk:C_(programming_language)/Archive_8#%22Hello,_world%22_example as referenced in the current page (https://en.wikipedia.org/w/index.php?title=C_(programming_language)&diff=930286305&oldid=930286262) as:
<!-- READ THIS BEFORE YOU EDIT! If you think there is a better way, first see talk page archive No. 8 for why. If you still want to change it, discuss it first. -->
#include <stdio.h>
int main(void)
{
printf("hello, world\n");
}
Looks like wrong use of pritnf where
print formatted (printf) is designed to work with a provided format as referenced on https://en.wikipedia.org/wiki/Printf_format_string#Syntax meaning that the correct code should look like:
#include <stdio.h>
int main(void)
{
printf("%s\n", "Hello world");
// ^^^^^^ - Notice format string for printf used
}
This should be updated for all printf mensions in this article. --Kreyren (talk) 23:19, 11 December 2019 (UTC)
- A printf format string need not have parameter format specifications. Adding them where not needed is distracting to the reader. --A D Monroe III(talk) 00:56, 26 June 2020 (UTC)
Source
In private conversation with Bjorn Sjostrup, he confirmed that previous compilers from other coders were considered as sources for good ideas, as was the norm for the time: we were building an industry, and the patent rights now claimed should be carefully examined as non-original work: bubble sorting and bitmapped fonts were part of this for sure, because I worked on them! — Preceding unsigned comment added by 90.197.51.50 (talk) 22:49, 7 July 2020 (UTC)
- That's a start. You might be able to find a reliable source. Private conversations aren't that. TEDickey (talk) 22:56, 7 July 2020 (UTC)
TempleOS
I agree that the IP's effort (diff) to add HolyC (linked to TempleOS) to the infobox is WP:UNDUE. In fact I can't think of a DUE way of mentioning HolyC or TempleOS at this article but any long-term C coders (hi Guy Macon) might like to review the stunning achievement of TempleOS (it's crazy but a magnificent achievement with, for example, JIT-compiled HolyC as the shell language) and think about what articles could link to it. Johnuniq (talk) 00:10, 26 July 2020 (UTC)
- (I am mostly an assembly-language programmer, but I can code in C if I have to.)
- HolyC: not to be confused with Holy See. :)
- It certainly does simplify things if the system's features are explicitly instructed to you by God...
- You can run it in a virtual machine: [ https://eleni.mutantstargoat.com/hikiko/holy-days-temple-os ]
- Rosetta Code has a category for programs written in HolyC: [ https://rosettacode.org/wiki/Category:HolyC ]
- Alas, the one thing HolyC isn't is a variation of the C programming language. If you look at the description here:[1] you will see that it is a new programming language with some similarities to C. --Guy Macon (talk) 00:58, 26 July 2020 (UTC)
- Thanks for the links. Johnuniq (talk) 01:40, 26 July 2020 (UTC)
A Commons file used on this page or its Wikidata item has been nominated for deletion
The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:
Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 14:18, 19 October 2020 (UTC)
About the Hello World Example
I think that the hello world example should be like this:
#include <stdio.h>
int main(){
printf("%s\n""Hello World!");
return 0;
}
—ThesenatorO5-2 (talk • contribs) 09:38, 25 June 2020 (UTC)
- That's incorrect too and will most likely result in a runtime crash. — Preceding unsigned comment added by Brett Alexander Hunter (talk • contribs)
- Hello world are examples of minimal standard-compliant code that perform the specific task of printing a message on the device's display/output. The code currently on the article is correct and requires no additional complications. Fbergo (talk) 15:53, 25 June 2020 (UTC)
As things stand right now, your second example will result in a compiler warning, won't it? You specifically indicate an 'int' return value but return nothing. That's anything but 'standard-conforming' as you call it.
Brian was brilliant at educating in that book. The way he told you something but also left off tidbits and crumbs for the lesson coming up.
The actual purpose of hello world is to get your environment up and running.
Cheers. — Preceding unsigned comment added by Brett Alexander Hunter (talk • contribs)
It should be like this.
#include <stdio.h>
int main(){
printf("%s\n", "Hello World!"); // Note that the two args should have a , between.
return 0;
}
01:05, 19 August 2020 (UTC)ThesenatorO5-2argue with me
- Nah, we should stick to the minimal version. There is no reason to break the string into two arguments. - MrOllie (talk) 01:14, 19 August 2020 (UTC)
In The ANSI C Programming Language book by the inventors of C Brian Kernighan and Dennis Ritchie, the example they used was as follows:
#include <stdio.h>
main()
{
printf("hello, world\n");
}
Although I must say that in order to get that to compile I had to make it "int main()" rather than just main. Thunderblood101 (talk) 21:12, 17 January 2021 (UTC)
- Even
int main(void), and withreturn 0;at the end. — Vincent Lefèvre (talk) 21:27, 17 January 2021 (UTC)
A Commons file used on this page or its Wikidata item has been nominated for deletion
The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:
Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 06:41, 30 June 2021 (UTC)
Pointer values
- Pass-by-reference is simulated in C by explicitly passing pointer values.
'Pointer values' is specifically ambiguous. Suggest 'addresses' instead. Also: 'pass-by-reference' seems new. The accepted terms are 'call by reference' and 'call by value' (with a third method unused but for Algol - 'call by name'). Also: it's not really 'simulated' either, is it? It's done. — Preceding unsigned comment added by Brett Alexander Hunter (talk • contribs) 01:18, 6 August 2020 (UTC)
arrays
I started to revise the text about arrays because it was outdated, slightly incorrect, and partially misleading. (As background info: I am a member of the ISO working group for C and contributor to GCC.) Martin.uecker (talk) 08:25, 21 November 2021 (UTC)
Italics
@Chumpih: I don't think MOS:TERM applies to this edit. It says A technical or other jargon term being introduced is often being mentioned as a word rather than (or in addition to) playing its normal grammatical role
, but in this case it is neither a technical term (rather, it is a proper name) nor is it being mentioned as a word. If the name of the language were 'Python' rather than 'B' I doubt anyone would write "A successor to the programming language Python". Ruбlov (talk • contribs) 15:25, 21 April 2022 (UTC)
- @Rublov, Given these are the introductions of the terms, as opposed to references to the terms, perhaps the italicisation is warranted. Chumpih t 15:41, 21 April 2022 (UTC)
- Actually, on further consideration, you're probably right. Apologies. Chumpih t 16:00, 21 April 2022 (UTC)
Order of sentences in the opening paragraph
Is there a good reason why the opening paragraph starts with “commonly in …” then one “decreasingly in …” then more “commonly in …”? I found this order slightly confusing. Osalbahr (talk) 01:39, 31 May 2022 (UTC)
- It's likely imperfect, as you identify. WP:DIY. Then perhaps WP:BRD or perhaps subsequent changes if your edits don't quite hit the mark. Chumpih t 21:24, 31 May 2022 (UTC)
"C(programming language)" listed at Redirects for discussion
An editor has identified a potential problem with the redirect C(programming language) and has thus listed it for discussion. This discussion will occur at Wikipedia:Redirects for discussion/Log/2022 August 16#C(programming language) until a consensus is reached, and readers of this page are welcome to contribute to the discussion. Steel1943 (talk) 21:09, 16 August 2022 (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:08, 18 August 2022 (UTC)