in reply to RFC - File::Util 4.x Series Pre-Release
1. Filename like - :a:b:c:d:e:f:g.txt - I think Mac
OS Classic support was dropped from Perl !
2. That's very sad that you use 5.006 and seems
not to support Unicode filenames processing, or you do?
3. Bigger problem with crospatform filenames
is case insensetivity and unicode normalization (on MacOSX). Need unicode for this.
Would be great to implement stuff to convert filenames to canonical form with this in mind.
> Illegal characters (i.e.- any type of newline character, tab, vtab, and the following / | * " ? < : > \),
It's not really clear to me what escape you are talking about and what characters are illegal. Escape for shell command line? What shell/what OS?
5. file_type, existent, can_write etc
I don't see any good reason to create wrappers to perl -X operators
6. Returns alphabetically sorted all file names in the directory specified if it exists
Do you mean ASCII sorted. To sort alphabetically you need unicode AND to know which locale to use.
> Recurse subdirectories
hm. there is no option to follow/not follow symlinks for directory? What about recursive symlinks?
i think any OS needs binmode:
> . Note that, despite what may be implied in "Programming Perl" (the Camel, 3rd edition) or elsewhere, :raw is not simply the inverse of :crlf. Other layers that would affect the binary nature of the stream are also disabled. See PerlIO, perlrun, and the discussion about the PERLIO environment variable.
> $ILLEGAL_CHR = qr/\\$NL\r\n\t\013\*\"\?\<\:\>/;
a) on Linux any character except NULL and '/' is legal
b) NULL is illegal.