FilePath rejects legal "wildcard" characters in file name

24 views
Skip to first unread message

Sivan

unread,
Jan 17, 2015, 3:12:40 PM1/17/15
to newspeak...@googlegroups.com
While working through the BraveNewWorldExplorer example, the debugger came up when iterating over a file name: all?q=puppy. This is a file that was downloaded with wget or some such. There's nothing illegal about the name. 


Sivan

unread,
Jan 17, 2015, 3:15:01 PM1/17/15
to newspeak...@googlegroups.com
FilePath rejects wildcard (MacOSX).png
Message has been deleted

Gilad Bracha

unread,
Jan 17, 2015, 8:38:56 PM1/17/15
to newspeak...@googlegroups.com
The ? character gets interpreted as a wildcard character, matching any single character at that position, e.g.: allxq=puppy, allAq=puppy and so on.  A pattern containing a wildcard does not specify a specific file, and so pattern: cannot really cope with a file with such a name.

Given that MacOS seems to allow the creation of such files there does seem to be a need for more sophistication in the file API.  


On Sat Jan 17 2015 at 12:16:33 PM Sivan <sivan...@gmail.com> wrote:
Attached screenshot
Reply all
Reply to author
Forward
0 new messages