12 Dec
2011
12 Dec
'11
7:27 p.m.
On Dec 12, 2011, at 4:44 PM, Fred Cisin wrote:
On Mon, 12 Dec 2011, Guy Sotomayor wrote:
That's just ugly (and I believe not correct)! ;-)
What I meant to type was:
([char])+[.[char][char][char]]
However, in the shell to match only 8.3 format names would be:
+(?)?(.?(???))
It's even more general than that. Many folks
have fallen into the
Microsoft (FAT) limitation that a file is [char]+.[char][char][char]
format for a file name.
char[char][char][char][char][char][char][char](.)[char][char][char]
There MUST be at least one character at the beginning of the filename. The
remaining 7 positions, and the three of the "extension" are padded out
with spaces if not used, and no non-space character can FOLLOW a space in
either field ("undefined" behavior results from embedded spaces (F 3.C)),
although the command line parser will treat any spaces in the command
line as delimiters. (It will assume that FILENAM .C or F 3.C are each two
items, not single names.)
That's the "on-disk" representation not what would be specified on the
command line.
TTFN - Guy