bindata/testdata
Tamir Duberstein ff362dd1f1 Use `filepath` everywhere instead of `path`
For non-slashed paths (e.g. Windows) `path` does the wrong thing.
Sadly this is not documented, but a cursory glance at the go sources
reveals that `filepath` uses `os.PathSeparator` everywhere while
`path` uses a literal `"/"`.
2015-07-02 11:44:17 -04:00
..
dupname Fix bug of knownFuncs usage when findFiles is called recursively 2014-12-09 22:07:31 +09:00
in Implements writing of TOC file. Refactors code for debug and release 2013-10-30 13:14:58 +01:00
out Use `filepath` everywhere instead of `path` 2015-07-02 11:44:17 -04:00
symlinkFile Implementation for following symlinks 2015-04-16 09:38:06 -04:00
symlinkParent Implementation for following symlinks 2015-04-16 09:38:06 -04:00
symlinkRecursiveParent Implementation for following symlinks 2015-04-16 09:38:06 -04:00
symlinkSrc Implementation for following symlinks 2015-04-16 09:38:06 -04:00
Makefile Better Makefiles 2015-05-11 21:39:32 -04:00