I have to ask you this question (just to keep sane), why are you "updating" boost from 1.39 to 1.50, given that the current version is 1.62? Degski Because a ‘big chief’ gave this order … I am not able to give you a technical reason to that … ☹ Jean

On 10/20/2016 10:50 AM, MAURICE Jean wrote:

...

I have to ask you this question (just to keep sane), why are you "updating" boost from 1.39 to 1.50, given that the >current version is 1.62? degski Hi, in fact there is a ‘technical reason’ : my client is a huge company. They have built their own Linux distribution based on REDHAT with standard and private tools added. Among these tools, there is boost 1.50.

Jean

Hello, I just wanted to hook in here. Even though their distribution ships boost 1.50 doesn't mean you cannot deliver your own version of boost. In fact I have built third-party packages that do exactly that (on Ubuntu though). For me this seems to be a matter of how your project is setup. Regards

Hi John, The first thing I would like to know is : Is "{m_pimpl={.}}" a correct regular expression ? If yes, what does it mean ? TIA Jean -----Message d'origine----- De : Boost-users [mailto:boost-users-bounces@lists.boost.org] De la part de John Maddock Envoyé : jeudi 20 octobre 2016 11:13 À : boost-users@lists.boost.org Objet : Re: [Boost-users] upgrade from boost 1.39 to boost 1.50. Issue with regex_match On 19/10/2016 13:41, MAURICE Jean wrote:

Hi,

I am 'upgrading' a huge C++ app from VS2005 (32bits) to VS2010 (64 bits) and boost 1.39 to boost 1.50. This app runs both under Windows and Linux.

In a function that searchs subdirectories and files of a given directory, we get the list of all the elements and then this list is filtered by :

if(true==boost::regex_match(sAdaptation, what, childNode.infoNode.rFullPathFilePattern))

*sAdaptation*is ".\TEST\un_noeud" (this subdirectory exists)

childNode.infoNode.rFullPathFilePattern is something like *{m_pimpl={.}}*

And regex_match always returns false.

If you can give me information about what is happening .

I don't see anything in the changelog that would indicate an issue there, and those releases are so far back my memory certainly won't help! So you will need to provide a test case - or at least a pattern and string for which regex_match fails for us to help further. John. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

So ... I spent a long time to step into the app with the debugger. The string "{m_pimpl={...}}" is what the debugger shows in childNode.infoNode.rFullPathFilePattern. And childNode.infoNode.rFullPathFilePattern is the third parameter of if(true==boost::regex_match(sAdaptation, what, childNode.infoNode.rFullPathFilePattern)) it cannot return true : right ? (in fact it is what happens) TIA Jean -----Message d'origine----- De : Boost-users [mailto:boost-users-bounces@lists.boost.org] De la part de John Maddock Envoyé : jeudi 20 octobre 2016 11:45 À : boost-users@lists.boost.org Objet : Re: [Boost-users] upgrade from boost 1.39 to boost 1.50. Issue with regex_match On 20/10/2016 10:17, MAURICE Jean wrote:

Hi John,

The first thing I would like to know is :

Is "{m_pimpl={.}}" a correct regular expression ?

No, it's just a view of the internals of something (the regex object?) You would need to call basic_regex::str() to get the actual stored regular expression, or else just stream the regex object to cout.

If yes, what does it mean ?

TIA Jean

childNode.infoNode.rFullPathFilePattern.m_pimpl.px->m_expression

error C2248: 'boost::basic_regex::m_pimpl' : cannot access private member declared in class boost::basic_regex' error C2248: 'boost::shared_ptr<T>::px' : cannot access private member declared in class 'boost::shared_ptr<T>' !! but the error gives me an information I didn't understand first m_pimpl is a 'variable' and not the 'final' string. I go back to the debugger .... Thanks for your help Jean