1) depends upon the external file names you want to distribute, and your audience. If you don't ship PRG's, SC*'s you can use whatever you want -- if you do ship source code, your customer's system is the determining factor.

2) I did not see any mention of the embedded space (blank character) in long file names, so will offer suggestion that you embed such long file names with embedded space(s) in quotes when coding on a command -- or whereever the parsing would not be able to tell the difference between a long file name with embedded blanks and separate operands on a command line.