Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Then the syntax supported by CVSnt in the Modules2 file is not just that of extended regular expressions - you've added in file globbing, or a subset thereof. (e.g. as described in http://www.faqs.org/docs/abs/HTML/globbingref.html) The statement "You can also mask certain files within a directory, or certain subdirectories using an extended regular expression." in http://www.cvsnt.org/manual/modules2.html is misleading. It ought to say you can use EREs or filename expansion metacharacters, and explain which ones you've implemented. Mixing both syntaxes sounds like a recipe for disaster though IMHO - how can you determine whether a '*' is an RE quantifier or a match-any-characters glob? (in e.g. 'gui.*.cpp') JK Tony Hoyle wrote: > John Kinson wrote: > >> Tony, your ERE example in the manual isn't right (unless you've >> implemented a non-standard RE engine). >> >> In the line >> >> / = myproject (*\.cpp$|*\.[ch]$|*/$) >> >> Surely that should either be >> >> / = myproject (.*\.cpp$|.*\.[ch]$|.*/$) >> >> or more simply >> >> / = myproject (\.cpp$|\.[ch]$|/$) >> > Actually all 3 should work, but the first one is a little bit more like > the way Windows users expect it to work (the regexp engine implicitly > translates * in the first character to .*). > > eg. you can use (*.cpp) and it'll work (but might bring back some > unexpected files in that case) > > Tony -- http://www.yellowradio.com/ If technology doesn't seem like magic, it's probably obsolete.