Message232557
The argument to open is a path. Some of those characters have a meaning in a path.
I ran a couple of quick experiments: "ab*c.txt" fails with an exception. ":16.txt" created a file, which I can do an 'ls' and cat (but not rm) on in git-bash, but I'm not sure where it actually is in the file system.
Open is just calling the OS to do the open, so if no error is raised, the *OS* (Windows) is not raising the error. I don't think there is a bug here, unless it is in Windows itself. |
|
Date |
User |
Action |
Args |
2014-12-12 16:20:10 | r.david.murray | set | recipients:
+ r.david.murray, tim.golden, zach.ware, steve.dower, iMath |
2014-12-12 16:20:10 | r.david.murray | set | messageid: <1418401210.55.0.251456676258.issue23039@psf.upfronthosting.co.za> |
2014-12-12 16:20:10 | r.david.murray | link | issue23039 messages |
2014-12-12 16:20:10 | r.david.murray | create | |
|