• @[email protected]
    link
    fedilink
    English
    23
    edit-2
    3 months ago

    I am very sorry to remind everyone about the existence of Visual Basic, but it has:

    • VbCrLf
    • VbNewLine
    • ControlChars.CrLf
    • ControlChars.NewLine
    • Environment.NewLine
    • Chr(13) & Chr(10)

    And I know what you’re asking: Yes, of course all of them have subtly different behavior, and some of them only work in VB.NET and not in classic VB or VBA.

    The only thing you can rely on is that “\r\n” doesn’t work.

    • @[email protected]
      link
      fedilink
      53 months ago

      I just learned that in Python, it’s fucking terrible. Python is a fucking mess and my next script will be in a different language.

      • qaz
        link
        fedilink
        English
        43 months ago

        Perhaps TS is not a terrible language for shell scripts after all

      • @[email protected]
        link
        fedilink
        33 months ago

        As a python lover, I have to ask, what don’t you like about it and what languages do you generally prefer?

        • @[email protected]
          link
          fedilink
          13 months ago

          I prefer strongly typed languages. Using bytes isn’t intuitive.

          Transforming certain data types into other data types is often not straightforward.

          The identation is the worst though. Let me format the code however I want.

  • r00ty
    link
    fedilink
    33 months ago

    Maybe c# has similar. There’s \r\n or \n like c++ and Environment.NewLine.

    Probably it’s similar in that Environment.NewLine takes into account the operating system in use and I wonder if endl in c++ does the same thing?

    • @[email protected]
      link
      fedilink
      43 months ago

      C# also has verbatim strings, in which you can just put a literal newline.

      string foo = @"This string 
      has a line break!";
      
    • @[email protected]
      link
      fedilink
      363 months ago

      It’s a very C++ thing that the language developers saw the clusterfuck that is stream flushing on the kernel and decided that the right course of action was to create another fucking layer of hidden inconsistent flushing.

      • @[email protected]
        link
        fedilink
        23 months ago

        programmers manage to do stupid shit in every language. i was wondering if there was a way to stop them, and golang comes close but maybe proves it can’t be done. idk!

    • @[email protected]
      link
      fedilink
      13 months ago

      Considering std::cout should only directly be used when you are too lazy to place breakpoints, I totally get the decision to auto-flush.

    • unalivejoy
      link
      fedilink
      English
      203 months ago

      Just because the box says something is flushable doesn’t mean you should flush it.

    • @[email protected]
      link
      fedilink
      53 months ago

      Unix needed only \n because it had complex drivers that could replace \n with whatever sequence of special characters the printer needed. Also, while carriage return is useful, they saw little use for line feed

      On dos (which was intended for less powerful hardware than unix) you had to actually use the correct sequence which often but not always was \r\n (because teleprinters used that and because it’s the “most correct” one).

      Now that teleprinters don’t exist, and complex drivers are not an issue for windows, and everyone prefers to have a single \n, windows still uses \r\n, for backward compatibility.

    • Arghblarg
      link
      fedilink
      13 months ago

      Bedeviled NXP/ARM SDK stdlib. Hate it, we need \n\r there. Why!!! What a PITA.

  • @[email protected]
    link
    fedilink
    23 months ago

    Kinda in Java, you can call System.out.println or you can call System.out.print and explicitly write the newline.

    • @[email protected]
      link
      fedilink
      23 months ago

      I haven’t looked at the code but I always assumed that println was a call to print with a new line added to the original input.
      Something like this:

      void print(String text) { ... }
      void println(String text) { this.print(text + '\n'); }
      
      • @[email protected]
        link
        fedilink
        23 months ago

        That is pretty much what it does except it doesn’t hardcode \n but instead uses the proper line ending for the platform it’s running on.

        • @[email protected]
          link
          fedilink
          13 months ago

          I haven’t worked with java for a couple of months now, currently working in Delphi, so could not remember the how else to do new line except backslash n on top of my head. :-)

  • Sibbo
    link
    fedilink
    33 months ago

    Wasn’t this {fmt} library merged into STL now? Does this solve this issue?

    Anyways, there was also a constant that is the OS line ending without a flush, right?

  • pelya
    link
    fedilink
    30
    edit-2
    3 months ago

    printf is superior and more concise, and snprintf is practically the only C string manipulation function that is not painful to use.

    Try to print a 32-bit unsigned int as hexadecimal number of exactly 8 digits, using cout. You can do std::hex and std::setw(8) and std::setfill('0') and don’t forget to use std::dec afterwards, or you can just, you know, printf("%08x") like a sane person.

    Just don’t forget to use -Werror=format but that is the default option on many compilers today.

    C++23 now includes std::print which is exactly like printf but better, so the whole argument is over.

    • @[email protected]
      link
      fedilink
      33 months ago

      I went digging in cppref at the format library bc I thought c++20 or c++23 added something cool.

      Found std::print and was about to reply to this comment to share it bc I thought it was interesting. Then I read the last sentence.

      Darn you and your predicting my every move /j