Hello John, Many thanks for the information you have provided. I am looking to use wildcards for my program, but not just for file matching. To overcome this I will write a wrapper function to convert * in to .*, but that should not be too difficult. Then I guess it's a case of RTFM for the rest. To solve your problem of wildcarding, may I suggest that you use Unix over DOS or perhaps create a couple of flags to incorprate either. I have noticed somthing else however with the current build. I'm getting C4786 warnings all over the place when I compile. I have tried putting #pragma warning(disable : 4786) at the start of my program, but this appears to have no effect. I wonder if it's something to do with the library. Remember I'm ising mscv6. Regards, Richard "John Maddock" <john@johnmaddock.co.uk> wrote in message news:014b01c43d89$1aec8aa0$307b0252@fuji...
Many thanks for your help and advice here. It helped me to solve my problem, the expression I was passing to the function was not valid. However, I have one more question. I know this is regular expressions here, but why am I not allowed to use "*tart* instead of "(.*)tart(.*)".
Or you could use .*tart.*
Boost regex implements three types of patterns:
Perl regular expressions (what you get by default) POSIX extended regular expressions. POSIX basic regular expressions.
The latter two are available by passing the appropriate flags to the regex constructor, for example:
boost::regex e("\(.*\)abc", boost::regex::basic | boost::regex::icase);
Is a case insensitive, POSIX basic expression.
In none of three supported grammars is *tart* a valid expression.
I assume you were wanting a wildcard for matching filenames? If so that's on my list of things to implement as well, but there are two competing and rather incompatible forms to choose from (Unix style wildcards, and MS-DOS style), which muddies the waters somewhat.
John.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost