• ulterno@programming.devEnglish
    4·
    6 hours ago

    Simple. \n when you just want a newline.
    println when you need to flush at the moment.

    Useful in case you are printing a debug output right before some function that might do bed stuff to buffers.

  • Oinks@lemmy.blahaj.zoneEnglish
    2·
    6 hours 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.

    • mmddmm@lemm.ee
      17·
      15 hours 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.

    • unalivejoy@lemm.eeEnglish
      16·
      18 hours ago

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

  • pelya@lemmy.world
    19·
    17 hours 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.

  • r00ty@kbin.life
    3·
    15 hours 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?

    • vithigar@lemmy.ca
      2·
      8 hours ago

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

      string foo = @"This string 
has a line break!";
    • Fonzie!@ttrpg.network
      1·
      30 minutes ago

      For me the answer is “Building backend applications with it instead of CLI applications, like Lerdorf intended.”

      But also "\n" because it’s easier and PHP_EOL is just an alias for "\n"; it’s not even platform-dependent.

  • Sibbo@sopuli.xyz
    3·
    18 hours 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?

  • palordrolap@fedia.io
    31·
    17 hours ago

    If endl is a function call and/or macro that magically knows the right line ending for whatever ultimately stores or reads the output stream, then, ugly though it is, endl is the right thing to use.

    If a language or compiler automatically “do(es) the right thing” with \n as well, then check your local style guide. Is this your code? Do what you will. Is this for your company? Better to check what’s acceptable.

    If you want to guarantee a Unix line ending use \012 instead. Or \cJ if your language is sufficiently warped.

    • edinbruh@feddit.it
      5·
      18 hours 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.