←back to thread

The provenance memory model for C

(gustedt.wordpress.com)
224 points HexDecOctBin | 1 comments | 30 Jun 25 09:25 UTC | HN request time: 0.208s | source
Show context
smcameron ◴[30 Jun 25 16:04 UTC] No.44424882[source]▶
Ugh. Are unicode variable names allowed in C now? That's horrific.
replies(5): >>44424985 #>>44425020 #>>44425869 #>>44426140 #>>44426336 #
1over137 ◴[30 Jun 25 16:17 UTC] No.44425020[source]▶
Horrific? You might not think so if your (human) language used a different alphabet.
replies(3): >>44425223 #>>44425239 #>>44425432 #
Joker_vD ◴[30 Jun 25 16:53 UTC] No.44425432[source]▶
My language uses Cyrillic and I personally prefer English-based keywords and variable names precisely because they are not words of my (human) language. It introduces an easy and obvious distinction between the machine-oriented and the human-oriented.
replies(2): >>44426725 #>>44435410 #
1. cryptonector ◴[01 Jul 25 16:15 UTC] No.44435410[source]▶
Yes, I also think the whole word should program in English.

That's half tongue in cheek. I am fluent in three languages, but I program "in English" and I greatly appreciate that my colleagues who are fluent in languages other than the ones I'm fluent in (except English) also do. Basically English is the world's lingua franca today. Nonetheless if a company in France wants to use French for their symbol names, or a company in Mexico wants to use Spanish for their symbol names, or a company in China wants to use Chinese for their symbol names, who am I to stop them?! Surely it's not my place.