←back to thread

The provenance memory model for C

(gustedt.wordpress.com)
225 points HexDecOctBin | 2 comments | | HN request time: 0.534s | source
Show context
smcameron ◴[] No.44424882[source]
Ugh. Are unicode variable names allowed in C now? That's horrific.
replies(5): >>44424985 #>>44425020 #>>44425869 #>>44426140 #>>44426336 #
1over137 ◴[] No.44425020[source]
Horrific? You might not think so if your (human) language used a different alphabet.
replies(3): >>44425223 #>>44425239 #>>44425432 #
1. ajross ◴[] No.44425223[source]
Little to no source code is written for single (human) language development teams. Sure, everyone would like the ability to write source code in their native language. That's natural.

Literally no one, anywhere, wants to be forced to read source written in a language they can't read (or more specifically in this case: written in glyphs they can't even produce on their keyboard). That idea, for almost everyone, seems "horrific", yeah.

So a lingua franca is a firm requirement for modern software development outside of extremely specific environments (FSB malware authors probably don't care about anyone else reading their cyrillic variable names, etc...). Must it be ASCII-encoded English? No. But that's what the market has picked and most people seem happy enough with it.

replies(1): >>44425925 #
2. OkayPhysicist ◴[] No.44425925[source]
> Little to no source code is written for single (human) language development teams.

This is blatantly false. I'd posit that a solid 90% of all source code written is done so by single, co-located teams (a substantial portion of which are teams of 1). That certainly fits the bill for most companies I've worked at.