File::parseAbsolutePath should strip multiple occurrences of separator char

The File class doesn’t normalize multiple occurrences of a separator character when parsing and normalizing the path in it’s File::parseAbsolutePath. E.g. a path /tmp//foo or /tmp///foo should be normalized to /tmp/foo. If that doesn’t happen functions like File::isAChildOf return the wrong result when e.g. checking if /tmp//foo/bar is a child of /tmp/foo.
Both Windows and Unix operating systems support the use of double slashes.

Cool, Thanks for the fast fix! Will try that as soon as i can. Just briefly looking at the code i wonder if that wouldn’t have a bad effect on windows network paths that start with \\foo.

Thanks, this commit should prevent issues with parsing UNC paths.