[ 
https://issues.apache.org/jira/browse/MINIFICPP-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gábor Gyimesi updated MINIFICPP-1636:
-------------------------------------
    Description: 
C++17 support allows us to use std::filesystem instead of the currently 
equivalent boost library calls. We should also investigate where 
std::filesystem could be used instead of a platform specific implementations.

Note: std::filesystem::last_write_time returns std::filesystem::file_time_type 
which uses a platform dependent clock. This makes it hard to replace the 
previous implementation as the time since epoch can be different in two 
systems, the conversion to time_t can be difficult and also out usage of time 
strings may be problematic. C++20 standardizes the 
std::filesystem::file_time_type with std::chrono::file_clock which solves these 
problems, so it may be better to implement this when we have full C++20 support.

  was:C++17 support allows us to use std::filesystem instead of the currently 
equivalent boost library calls. We should also investigate where 
std::filesystem could be used instead of a platform specific implementations.


> Use std::filesystem instead of boost and platform specific implementations
> --------------------------------------------------------------------------
>
>                 Key: MINIFICPP-1636
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1636
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Improvement
>            Reporter: Gábor Gyimesi
>            Priority: Minor
>              Labels: MiNiFi-CPP-Hygiene
>
> C++17 support allows us to use std::filesystem instead of the currently 
> equivalent boost library calls. We should also investigate where 
> std::filesystem could be used instead of a platform specific implementations.
> Note: std::filesystem::last_write_time returns 
> std::filesystem::file_time_type which uses a platform dependent clock. This 
> makes it hard to replace the previous implementation as the time since epoch 
> can be different in two systems, the conversion to time_t can be difficult 
> and also out usage of time strings may be problematic. C++20 standardizes the 
> std::filesystem::file_time_type with std::chrono::file_clock which solves 
> these problems, so it may be better to implement this when we have full C++20 
> support.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to