windwos ros2-eloquent-debug std::regex re(regex) running error

[cjsJack]

Hi, I am using ros2-eloquent-debug in windows, using visual studio 2015,
and I am building image_common package from https://github.com/ros-perception/image_common , and when I run list_transport project of image_common package, it failed when running list_transports.exe
So, I debug and find the reason is from pluginlib package from https://github.com/ros/pluginlib ,there is a syntax error about std::regex re(regex); in split.hpp from C:\dev\ros2-eloquent-debug\include\pluginlib\impl\split.hpp 45 line, and the parameter regex of std::regex re(regex) will become "\\" in windows system, because C:\dev\ros2-eloquent-debug\include\pluginlib\impl\filesystem_helper.hpp already define #define CLASS_LOADER_IMPL_OS_DIRSEP '\\'
so std::regex re("\\") will fail when running project. It is running error, I already test in vs2015, vs2017, vs2019, they all run error std::regex re("\\")
Because give me some advice, thanks,
jack

[dirk-thomas]

ROS 2 Eloquent officially only supports Visual Studio 2019 (see https://index.ros.org/doc/ros2/Releases/Release-Eloquent-Elusor/).

The C++ compiler in VS 2015 might just be too old to understand the used syntax. Therefore I will go ahead and close this ticket.

[dirk-thomas]

Reopening - I missed that you are describing a runtime error in the regex and that you see the same problem with VS 2019.

[cjsJack]

I try run the same project list_transports.exe in ros2-dashing-debug of windows, finally, it also run error. And also I debug, find problem is same, because of std::regex re("\\"), My team have a project, and the project has the same problem like running list_transports.exe, will appear running error because of std::regex re("\\"). If you have some solution, please give me some advice Thanks , jack Dirk Thomas <notifications@github.com> 于2019年12月5日周四 上午12:39写道：

…

Reopening - I missed that you are describing a runtime error in the regex and that you see the same problem with VS 2019. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#170?email_source=notifications&email_token=AKSXUHNSOZATNKONP2UT5JTQW7MLTA5CNFSM4JVI7SB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF5UQYI#issuecomment-561727585>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKSXUHJLFQWFQ6GCKR2SBE3QW7MLTANCNFSM4JVI7SBQ> .