12 Dec
2011
12 Dec
'11
7:49 p.m.
On 12 Dec 2011 at 16:44, Fred Cisin wrote:
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.)
Microsoft (Patterson) lifted THAT directly from CP/M.
Who did Gary Kildall lift it from?
ISIS :)
From the ISIS-II user's guide:
"Some ISIS-II commands allow you to specify filenames using a wild
card construct. This means you can use an asterisk (*) or a question
mark (?) to replace some or all of the characters in a name or
extension. These special characters mean match anything when
searching a directory for a filename. For example,
name. * - means match any filename with name and any
extension or without an extension.
* . extension - means match any filename with extension and any
name."
--Chuck