I cannot figure out why this is failing so consistently. I feel like there is some small thing I am doing that is causing it to fail to parse the path.

use warnings;
use strict;

use IO::File;
use feature('say');

sub openFile{
    my $file = shift;

    #open my $fh, '>' , $file or die $!;

    my $fh = IO::File->new();
    if ($fh->open(">> $file")){
        say "I opened $file";
        $fh->close;
    } else { 
    say "failed to open $file $! ";
    }
}

openFile('C:\Users\Shain\AppData\Roaming\WaterAccount\file.log');
openFile("C:\Users\Shain\AppData\Roaming\WaterAccount\file.log");

openFile('$ENV{APPDATA}\WaterAccount\file.log');
openFile("$ENV{APPDATA}\WaterAccount\file.log");

openFile('C:\\Users\\Shain\\AppData\\Roaming\\WaterAccount\\file.log')
+;
openFile("C:\\Users\\Shain\\AppData\\Roaming\\WaterAccount\\file.log")
+;

openFile('$ENV{APPDATA}\\WaterAccount\\file.log');
openFile("$ENV{APPDATA}\\WaterAccount\\file.log");

openFile('C:\/Users\/Shain\/AppData\/Roaming\/WaterAccount\/file.log')
+;
openFile("C:\/Users\/Shain\/AppData\/Roaming\/WaterAccount\/file.log")
+;

openFile('C:/Users/Shain/AppData/Roaming/WaterAccount/file.log');
openFile("C:/Users/Shain/AppData/Roaming/WaterAccount/file.log");

openFile('$ENV{APPDATA}/WaterAccount/file.log');
openFile("$ENV{APPDATA}/WaterAccount/file.log");
[download]

Output:

C:\Users\OWNER\Documents\Work\Perl>perl file.pl
Unrecognized escape \S passed through at file.pl line 22.
Unrecognized escape \A passed through at file.pl line 22.
Unrecognized escape \R passed through at file.pl line 22.
Unrecognized escape \W passed through at file.pl line 22.
Unrecognized escape \W passed through at file.pl line 25.
failed to open C:\Users\Shain\AppData\Roaming\WaterAccount\file.log No
+ such file
 or directory
failed to open C:SERSSHAINAPPDATAROAMINGWATERACCOUNT♀ILE.LOG Inv
+alid argument
failed to open $ENV{APPDATA}\WaterAccount\file.log No such file or dir
+ectory
failed to open C:\Users\OWNER\AppData\RoamingWaterAccount♀ile.lo
+g Invalid argume
nt
failed to open C:\Users\Shain\AppData\Roaming\WaterAccount\file.log No
+ such file
 or directory
failed to open C:\Users\Shain\AppData\Roaming\WaterAccount\file.log No
+ such file
 or directory
failed to open $ENV{APPDATA}\WaterAccount\file.log No such file or dir
+ectory
failed to open C:\Users\OWNER\AppData\Roaming\WaterAccount\file.log No
+ such file
 or directory
failed to open C:\/Users\/Shain\/AppData\/Roaming\/WaterAccount\/file.
+log No suc
h file or directory
failed to open C:/Users/Shain/AppData/Roaming/WaterAccount/file.log No
+ such file
 or directory
failed to open C:/Users/Shain/AppData/Roaming/WaterAccount/file.log No
+ such file
 or directory
failed to open C:/Users/Shain/AppData/Roaming/WaterAccount/file.log No
+ such file
 or directory
failed to open $ENV{APPDATA}/WaterAccount/file.log No such file or dir
+ectory
failed to open C:\Users\OWNER\AppData\Roaming/WaterAccount/file.log No
+ such file
 or directory
[download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.