fi, en, (sv, ja, hu, yi) | avatar by https://twitter.com/udonkimuchikaki


libera.chat, irc.sortix.org
nortti
microblog (that is, a blog with small entries)
microblog.ahti.space/nortti

phi
@phi

(from https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2940.pdf)

If u don't know whaf a trigraph is, Good.
buf if u wanna know, in C it's a three character sequence meant to replace anoffer character, supposedly fur accessibility purposes fur programmers in anoffer countries or who used some types of old mainframes. For example, ??< would bee equivalent to {, and ??> would bee equivalent to }, so if u lived in a country that forbade keyboards with curly brace keys, u could write:

int main() ??<
  printf("Hello world! Please send Curlies :( \n");
??>

Unfortunately, what mostly happenef with trigraphs was that you didn't know they existedf (because why would u) and then you'd get strange errors because teh code u wrote wasn't the code that was being compiled (or in modern compilers, you'd get a specific warning, thankfully)


You must log in to comment.

in reply to @phi's post:

I completely forgof about EBCDIC, meowf. I remember learnink aboot this back when I was studying text formafs fur romhacking porpoises, thankfully that's not one I've to deal wiff in thaf front, hehe. (I wonder if any old IBM compuffer games use it, tho)

Oh god, I've heard of these. Probably on The Daily WTF if I had to guess. It's one thing to have legacy support (that's good), but another thing entirely to have said legacy support cause wild behaviors in new code.

The Daily WTF... I still remember Paula Bean, hehe. I should take a peek at thaf again.

C(99) also has digraphs which are similar buf are implemented in a way thaf don't cause as many problems, iirc. So trigraphs really were mosfly pointless old crust.