Unsuccessful %s on filename containing newline

(W newline) A file operation was attempted on a filename, and that operation failed, PROBABLY because the filename contained a newline, PROBABLY because you forgot to chomp() it off. See chomp in the perlfunc manpage.

########
# doio.c [Perl_my_stat Perl_my_lstat]

use warnings 'io' ;
stat "ab\ncd";
lstat "ab\ncd";
no warnings 'io' ;
stat "ab\ncd";
lstat "ab\ncd";
EXPECT
Unsuccessful stat on filename containing newline at - line 3.
Unsuccessful stat on filename containing newline at - line 4.
[download]

########
# pp_sys.c [pp_stat]
use warnings 'newline' ;
stat "abc\ndef";
no warnings 'newline' ;
stat "abc\ndef";
EXPECT
Unsuccessful stat on filename containing newline at - line 3.
[download]

    no warnings 'newline';
    next if -d "$dir/$current_filename";
[download]

Strange most operating systems disallow one of "/" and "\"...

root@XXXX:/tmp/testme
# touch \\
root@XXXX:/tmp/testme
# ls -rlt
total 0
-rw-r--r--   1 root     system            0 Feb 15 15:39 \
[download]

But...

You're right about / ! Don't use the directory separator! How embarrassing! Actually, it ,is legal, but far too problematic. I'll have to skip that one for now.

If I'm writing a test of the OS's file system, I should use all documented legal characters to create directories & files as part of that test.

Due to NDA, I don't feel comfortable saying which UNIX flavor I'm dealing with.

No, I am creating $dir and $current_filename using random ASCII values > 0 and < 128. I need to keep the newlines and other funky characters as-is. I think I'm only having trouble with newlines at this point.

You aren't telling us if the directory exists or not. Perl only gives you a helpfull warning, just in case you are trying to stat a file/directory with a newline in it - which would be a common programming error.

If you want to avoid the warning, just use

{ no warnings 'newline';
  next if -d "$dir/$current_filename";
};
[download]