As it's the calling application that validates filenames passed to the BDOS, you can even create lower-case filenames which future calls are unable to access if the application passes a fully-uppercase filename.Dropping by to observe that CP/M (at the API level) doesn't place any restrictions on filenames except they can't contain question marks. MBASIC 5.21, for example, doesn't do any validation on the filename, so you can save and reload a file called "*.BAS" without issues. Or FOO.BAS and Foo.BAS as separate files.
You are at least guaranteed 7-bit characters, because the top bits are used for file attributes.
With the above example, the CCP (the command console) won't be able to manipulate Foo.BAS in any way, such as deleting or renaming or stat'ing (info) it. You would only be able to manipulate it back in MBASIC (or anything else that does not force-uppercase filenames).Statistics: Posted by jgharston — Wed Aug 28, 2024 9:42 pm