Brandon Allbery via RT wrote: >It's also less than awesome that POSIX, at least, doesn't let you confirm >that a filename is syntactically valid,
At the syscall interface it's very simple: any sequence of non-nul octets may be used as a pathname. Since the pathname is passed in nul-delimited form, this is not so much a rule about what's permitted as about what's representable. Any rules beyond that about filename format (limited length, limited character repertoire, or whatever) are enforced by the kernel, and use of invalid names will produce appropriate syscall errors (such as ENAMETOOLONG). Perl 6 doesn't need to know about those rules that are enforced by the kernel. The syscall errors are sufficient. What Perl 6 *does* need to know about is the syntax at the syscall interface: that a pathname cannot contain a nul, and the manner in which a pathname splits into filenames at directory separators. -zefram
