Announcement

Collapse
No announcement yet.

C++17 Filesystem Support Lands In LLVM's Libc++ Library

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • C++17 Filesystem Support Lands In LLVM's Libc++ Library

    Phoronix: C++17 Filesystem Support Lands In LLVM's Libc++ Library

    This week support for the official C++17 "filesystem" feature landed within LLVM's libc++ standard library...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    If the committee keeps fleshing out C++ it might be worth reconsidering it as a programming option.

    Comment


    • #3
      Is that libc++ filesystem support based on native system calls, or is it a wrapper around the POSIX functions in libc?

      Comment


      • #4
        Originally posted by wizard69 View Post
        If the committee keeps fleshing out C++ it might be worth reconsidering it as a programming option.
        The way they keep fleshing out C++ is a great upgrade path for existing projects, and new projects in teams who won't be adopting a new language any time soon. It allows them to preserve all their existing base and still have access to modern programming features. Of course, for projects starting from scratch I'll always prefer Rust, Go or D, depending on the context.

        Comment


        • #5
          Originally posted by dwagner View Post
          Is that libc++ filesystem support based on native system calls, or is it a wrapper around the POSIX functions in libc?
          I haven't looked at it but I presume it will be things like path concatenation etc., which is implemented mainly as a library only.

          Comment


          • #6
            Originally posted by jacob View Post

            I haven't looked at it but I presume it will be things like path concatenation etc., which is implemented mainly as a library only.
            No, it is file system access. POSIX style so not fully 'native' on Windows and macOS but perfectly usable, and in fact driven by Microsoft. The committee is also coming with network module, though it was been postponed.

            I would still prefer Qt though

            Comment


            • #7
              It is both file access and classes for path concatenation/trimming etc., It's based on Boost::Filesystem, if I'm correct, but not sure how much of the original library features were standardized. It may be that it's "driven by Microsoft", but it lacks some "Windows features", afaik, most prominent of these is ACLs - standard unix rwx is supported only.

              Comment


              • #8
                Originally posted by jacob View Post

                The way they keep fleshing out C++ is a great upgrade path for existing projects, and new projects in teams who won't be adopting a new language any time soon. It allows them to preserve all their existing base and still have access to modern programming features. Of course, for projects starting from scratch I'll always prefer Rust, Go or D, depending on the context.
                It also helps these projects amputate their boost dependency. There will be very little excuse to need boost in the future (I can only hope!).

                Comment

                Working...
                X