Re^4: Filename Surrounded by Quotes in a Scalar Variable Causes Open to Fail

Understood. You're right. If Perl started removing quote characters without permission that would open the door to all sorts of unintended consequences.

I'm focused on developing on Windows at the moment, and I forgot about the other environments (*nix, etc.) that have different rules and allow different characters in filenames.

Thanks again for your input and clarification.

"It's not how hard you work, it's how much you get done."

Comment on Re^4: Filename Surrounded by Quotes in a Scalar Variable Causes Open to Fail

Replies are listed 'Best First'.
Re^5: Filename Surrounded by Quotes in a Scalar Variable Causes Open to Fail by Marshall (Canon) on Sep 03, 2020 at 22:51 UTC
I currently develop Perl code exclusively on Windows. However, some of my clients run my code on Unix and it almost always works even though I don't test it. My code does not create any filename that would not be a proper Perl variable name. That is more restrictive than it needs to be. However, if I create file "abc_123" (no spaces in the file name) from "abc 123" that does not seem to cause any significant issues for Windows users - they get it.	[reply]

Replies are listed 'Best First'.

Re^5: Filename Surrounded by Quotes in a Scalar Variable Causes Open to Fail
by Marshall (Canon) on Sep 03, 2020 at 22:51 UTC

I currently develop Perl code exclusively on Windows. However, some of my clients run my code on Unix and it almost always works even though I don't test it. My code does not create any filename that would not be a proper Perl variable name. That is more restrictive than it needs to be. However, if I create file "abc_123" (no spaces in the file name) from "abc 123" that does not seem to cause any significant issues for Windows users - they get it.

[reply]