Re: Illegal characters in windows filenames?

Have you tried encapsulating the filename in quotes for your filetest? The O/S you have uses question marks as single character wildcards. You don't get a filename match because it maches ONE character and doesn't try with "nothing" in that spot(as opposed to a NULL). I believe enclosing the name in quotes might be the trick in the short term.

Comment on Re: Illegal characters in windows filenames?

Replies are listed 'Best First'.
Re: Re: Illegal characters in windows filenames? by HamNRye (Monk) on Feb 10, 2004 at 20:39 UTC
One of the first things I did was try enclosing the filename in quotes. It's interesting you mention the "?" being used for globbing. When I enclose the file name in quotes in the shell, tools like xcopy work fine, but Perl cannot see the files. So does the perl filetest glob?? I'm thinking not. I'm wondering if the DOS shell passes that along expecting globbing to take care of the unsupported charachter. If that's the case, I can try replacing the "?" in the file names with literal 0x3F's. Hmm, I'll be giving it a try.	[reply]

Replies are listed 'Best First'.

Re: Re: Illegal characters in windows filenames?
by HamNRye (Monk) on Feb 10, 2004 at 20:39 UTC

One of the first things I did was try enclosing the filename in quotes. It's interesting you mention the "?" being used for globbing. When I enclose the file name in quotes in the shell, tools like xcopy work fine, but Perl cannot see the files. So does the perl filetest glob?? I'm thinking not.

I'm wondering if the DOS shell passes that along expecting globbing to take care of the unsupported charachter. If that's the case, I can try replacing the "?" in the file names with literal 0x3F's. Hmm, I'll be giving it a try.

[reply]