On Thu, Aug 8, 2013 at 11:14 PM, Paolo Carlini <paolo.carl...@oracle.com> wrote: > In my humble opinion involving the whole std::bitset container for a syntax > option is way overkill. Do you really have to do overloading between size_t > and that type? Or maybe you can use a type *smaller* than unsigned int.
The n3376 standard specified the following constructor: ... explicit basic_regex(const charT* p, flag_type f = regex_constants::ECMAScript); basic_regex(const charT* p, size_t len, flag_type f = regex_constants::ECMAScript); ... So flag_type shall not be the same as size_t. I don't know if when I switch flag_type from unsigned int to, say, unsigned short, conflicts will appear in 16bit archtectures. -- Tim Shen
