Regex failure when specifying path using backslashes (i.e. Windows-style).

[seraku24]

Consider the following commands:
haxelib run checkstyle -s tests/unit/src (Unix-style path)
haxelib run checkstyle -s tests\unit\src (Windows-style path)

On Windows, both commands run; however, the second one results in errors for each file processed. Here is an example of the output, when run against the haxe-flixel project:

tests\unit\src/FlxAssert.hx:1: character 0 : Error: Check AvoidStarImport failed: regexp.c(115) : Regexp compilation error : PCRE does not support \L, \l, \N{name}, \U, or \u in tests\unit\src:flixel:math:FlxRandomTest:.*?FlxAssert$
Stacktrace:
Called from /usr/local/lib/haxe/std/neko/_std/EReg.hx line 33
Called from /usr/local/lib/haxe/std/neko/_std/EReg.hx line 22
Called from checkstyle/Checker.hx line 288
Called from checkstyle/Checker.hx line 268

From a quick review of the code, the function Checker.checkForExclude() appears to only handle forward slashes. I suspect the escaping logic could be updated to something like the following:

var slashes = ~/[/\\]/g;
cls = slashes.replace(cls, ":");
for (exclude in excludesForCheck) {
	var regStr:String = slashes.replace(exclude, ":") + ":.*?" +
		cls.substring(cls.lastIndexOf(":") + 1, cls.length) + "$";
	var r = new EReg(regStr, "i");
	if (r.match(cls)) return true;
}