optional {}.
-
-
Replying to @rygorous @TimSweeneyEpic
also far fewer precedence levels with | on the same level as binary +, & << >> on the same level as binary *.
2 replies 0 retweets 2 likes -
Replying to @rygorous @TimSweeneyEpic
and make DOS use - for arguments, / for path name separators, trailing : for NUL, CON, AUX, LPT1 etc. not optional.
1 reply 0 retweets 9 likes -
Replying to @rygorous @TimSweeneyEpic
make Unicode aware of >65535 CPs and spec UTF-8 before Windows ever tries to settle for 16-bit chars.
2 replies 0 retweets 13 likes -
Replying to @rygorous @TimSweeneyEpic
give CP/M a line discipline so CP/M and DOS text files have LF not CRLF line endings
2 replies 0 retweets 8 likes -
Replying to @rygorous @TimSweeneyEpic
(I'm pretty sure I could go on this for a long time, but I think that's enough for now!)
3 replies 0 retweets 0 likes -
Replying to @rygorous @TimSweeneyEpic
It’s amazing to think how all of these are very low-tech “simple” things, if only they were done N years ago;
2 replies 0 retweets 2 likes -
…would have saved enormous amount of pain & hassle today.
2 replies 0 retweets 1 like -
Replying to @aras_p @TimSweeneyEpic
Here's another one: make C-style casts require a keyword, say "cast(type) x" or Rust-style "x as type".
1 reply 0 retweets 3 likes -
poof, I just made C-style casts greppable and dropped the grammar complexity of C++ from "undecidable" down to "context-sensitive"(*).
2 replies 0 retweets 11 likes
Pls fix C++ now.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.