Made with KolourPaint and screenshots from Kate (with the GitHub theme).

  • HiddenLayer555@lemmy.mlOPEnglish
    1·
    1 day ago

    any new keyword could break backwards compatibility

    Wouldn’t that happen anyway with variable and function names? Any type other than primitive/built in ones are usually camel case so lower case keywords are more likely to clash with single word variable and function names, unless you restrict the cases of those too or allow keyword overriding or something.

    • sus@programming.dev
      2·
      1 day ago

      Yeah, it’s in my edit I realized the same thing. I’m thinking it doesn’t actually really make sense and the real reason is more “the specific way C does it causes a lot of problems so we’re not poking syntax like that with a 10 foot pole” + “it makes writing the parser easier” + maybe a bit of “it makes grepping easier”

      • HiddenLayer555@lemmy.mlOPEnglish
        1·
        16 hours ago

        One thing that annoyed me about C# as a Java guy is that it really wants you to use camel case for function and property names, even private ones. I don’t like it specifically because it’s hard to differentiate between a function/property and a type.

        But C# has quite a few keywords and seem to like adding them more than Java.

        Maybe that’s their way of ensuring keywords don’t clash with stuff?