←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: 0s | source
Show context
jvanderbot ◴[30 Jun 25 12:55 UTC] No.44422693[source]▶
I love Rust, but I miss C. If C can be updated to make it generally socially acceptable for new projects, I'd happily go back for some decent subset of things I do. However, there's a lot of anxiety and even angst around using C in production code.
replies(6): >>44422779 #>>44423128 #>>44423371 #>>44423771 #>>44425323 #>>44433479 #
mikewarot ◴[30 Jun 25 13:02 UTC] No.44422779[source]▶
If you can stomach the occasional Begin and End, and a far less confusing pointer syntax, Pascal might be the language for you. Free Pascal has some great string handling, so you never have to worry about allocating and freeing them, and they can store gigabytes of text, even Unicode. ;-)
replies(2): >>44422784 #>>44422867 #
jvanderbot ◴[30 Jun 25 13:11 UTC] No.44422867[source]▶
If my fellow devs cringe at C, imagine their reaction to Pascal
replies(1): >>44423210 #
mikewarot ◴[30 Jun 25 13:45 UTC] No.44423210[source]▶
C has all the things to hate in a programming language

  CaSe Sensitivity
  Weird pointer syntax
  Lack of a separate assignment token
  Null terminated strings
  Macros - the evil scourge of the universe
On the plus side, it's installed everywhere, and it's not indent sensitive
replies(5): >>44423261 #>>44424125 #>>44424253 #>>44424648 #>>44430684 #
1. ioasuncvinvaer ◴[30 Jun 25 14:55 UTC] No.44424125{3}[source]▶
Except for null terminated strings these don't seem like mayor issues to me. Can you elaborate?