MSVC 2008 tr1::regex ignores icase flag?

[Arnold Smit]

Group,

MSVC 2008 seems to have a bug in their tr1::regex<> class.
The following code gives: true & false

#include <regex>
#include <iostream>
using namespace std;
int main()
{
tr1::basic_regex<char> regex("[A-Z]+", tr1::regex::ECMAScript | tr1::regex::icase);
cout<< std::boolalpha << tr1::regex_match("MATCH", regex) << endl; // gives true
cout<< std::boolalpha << tr1::regex_match("MaTcH", regex) << endl; // gives false ?
}

Shouldn't the flag tr1::regex::icase cause the regex to be case insensitive?
Is there a way to accomplish 'ignore case' in the shipped msvc 2008 tr1::regex class,
or should i start looking into boost::regex?

Regards Arnold

 

[Balog Pal]

#include <regex>
#include <iostream>
using namespace std;
int main()
{
tr1::basic_regex<char> regex("[A-Z]+", tr1::regex::ECMAScript |
tr1::regex::icase);
cout<< std::boolalpha << tr1::regex_match("MATCH", regex) << endl; //
gives true
cout<< std::boolalpha << tr1::regex_match("MaTcH", regex) << endl; //
gives false ?
}

Shouldn't the flag tr1::regex::icase cause the regex to be case
insensitive?
Is there a way to accomplish 'ignore case' in the shipped msvc 2008
tr1::regex class,
or should i start looking into boost::regex?

Does enum having icase defined an operator |?
If not your ctor calls an unintended overload, where 2nd param is size_t
len, and the third picks up default flags = ECMAScript...). Try to cast the
second arg to flag_type or whatever.

 

[Balog Pal]

#include <regex>
#include <iostream>
using namespace std;
int main()
{
tr1::basic_regex<char> regex("[A-Z]+", tr1::regex::ECMAScript |
tr1::regex::icase);
cout<< std::boolalpha << tr1::regex_match("MATCH", regex) << endl; //
gives true
cout<< std::boolalpha << tr1::regex_match("MaTcH", regex) << endl; //
gives false ?
}

Shouldn't the flag tr1::regex::icase cause the regex to be case
insensitive?
Is there a way to accomplish 'ignore case' in the shipped msvc 2008
tr1::regex class,
or should i start looking into boost::regex?

Does enum having icase defined an operator |?

Yes it has.

If not your ctor calls an unintended overload, where 2nd param is size_t
len, and the third picks up default flags = ECMAScript...). Try to cast
the second arg to flag_type or whatever.

This is not the problem for the case. (though one can be hit by it creating
the bitmask in a separate variable that is int or like...)

As I read the msdn page
http://msdn.microsoft.com/en-us/library/bb982727.aspx#formatflags
IUC the case-insensitive comparision modifier only applies to "ordinary"
characters, not [] sets.

Reading the part of standard implies similar, icase is mentioned matching
char to char, and matching against a character class, not in the bullet with
range.