• Croquette@sh.itjust.works
      4·
      2 days 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.

        • Croquette@sh.itjust.works
          1·
          19 hours 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.

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

  • ulterno@programming.devEnglish
    16·
    2 days ago

    Simple. \n when you just want a newline.
    endl 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.

    Edit: I wrote println instead of endl somehow. Guess I need more downtime

      • pelya@lemmy.world
        3·
        2 days ago

        It depends on whether you are printing to a terminal or to a file (and yes the terminal is also a file), and even then you can control the flushing behaviour using something like unbuffer

    • mmddmm@lemm.ee
      29·
      3 days 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.

      • jdeath@lemm.ee
        2·
        2 days 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!

    • Rednax@lemmy.world
      1·
      2 days 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@lemm.eeEnglish
      16·
      3 days ago

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

  • pelya@lemmy.world
    21·
    3 days 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.

    • SqueakyBeaver@lemmy.blahaj.zone
      3·
      2 days 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

  • palordrolap@fedia.io
    3·
    3 days 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.

    • pelya@lemmy.world
      3·
      2 days ago

      Ah don’t worry, if you do fopen(file, "w") on Windows and forget to use "wb" flag, it will automatically replace all your \n with \r\n when you do fwrite, then you will try to debug for half a day your corrupted jpeg file, which totally never happened to me because I’m an experienced C++ developer who can never make such a novice mistake.

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