Re: [Boost-users] [regex] Why pattern anchored at buffer end ($)alsomatch for (\x0c)FF, (\x0d)CR

From: Chandan Nilange (chandan_nilange_at_[hidden])
Date: 2008-02-20 00:19:29

I am restarting this old thread.

My Question:

How to modify Boost regex library, to match perl
behavior, such that, I only get pattern matches
after/before \n and ignore (\x0c)FF, (\x0d)CR
for  $ & ^  anchored patterns ?

Regards,
Chandan

John Maddock wrote:

>Chandan Nilange wrote:
>  
>
>>Hello John,
>>
>>I not very clear.
>>
>>So do you mean that -
>>
>>$ & ^ matching pattern after/before any  (\x0c)FF,
>>(\x0d)CR is right PCRE /m modifier behaviour.
>>    
>>
>
>I believe so, but deciding what the right behaviour
should be is not 
>necessarily easy: Perl has the luxury that it
controls File IO as well as 
>regexes: in contrast Boost.Regex is designed to
accept text from all kinds 
>of sources and platforms.  Most applications will in
any case regard an 
>isolated \r or \n as a line break, as well as \r\n. 
Likewise in what sense 
>does a form-feed *not* start a new line? :-)
>
>HTH, John. 
>
>_______________________________________________
>Boost-users mailing list
>Boost-users_at_[hidden]
>http://lists.boost.org/mailman/listinfo.cgi/boost-users
>  
>

      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ