Talk:C (programming language)/Archive 17

Archive 10

←

Archive 15

Archive 16

Archive 17

Why are characters and booleans irelevant to C programming?

Referencing https://en.wikipedia.org/w/index.php?title=C_(programming_language)&diff=930371741&oldid=930367380&diffmode=source

@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)