lmi-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lmi-commits] [lmi] master 271a1b8 09/33: Note a deferred boost-migratio


From: Greg Chicares
Subject: [lmi-commits] [lmi] master 271a1b8 09/33: Note a deferred boost-migration question
Date: Mon, 3 May 2021 08:15:51 -0400 (EDT)

branch: master
commit 271a1b891f725a48be79e745ce8388e8f6021465
Author: Gregory W. Chicares <gchicares@sbcglobal.net>
Commit: Gregory W. Chicares <gchicares@sbcglobal.net>

    Note a deferred boost-migration question
---
 path_utility.cpp | 1 +
 1 file changed, 1 insertion(+)

diff --git a/path_utility.cpp b/path_utility.cpp
index ee5d9d0..a0c273b 100644
--- a/path_utility.cpp
+++ b/path_utility.cpp
@@ -253,6 +253,7 @@ fs::path serial_file_path
 /// A try-block is necessary because fs::remove() can throw. The
 /// postcondition is asserted explicitly at the end of the try-block
 /// because that fs::remove() documentation is still unclear:
+///   BOOST !! Is this still true of std::filesystem?
 /// apparently it mustn't fail without throwing, yet it doesn't throw
 /// on an operation that must fail, like removing a file that's locked
 /// by another process as in the motivating example above.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]