3 ms·
> that was written to emulate the look and feel of CP/M. And that’s how DOS and then Windows ended up with “/” as the command-line option indicator and therefo
by layer8 3y ago
> that was written to emulate the look and feel of CP/M.
And that’s how DOS and then Windows ended up with “/” as the command-line option indicator and therefore “\” as the directory separator.
- ok123456 3y agoCP/M didn't have directories until 3.0, which was released in 1983. DOS didn't have them until 2.0. The backslash was chosen because the forward slash was used for arguments. This convention was taken from other timesharing operating systems of the day.
- deleted 3y ago[deleted]
- lproven 3y agoThis is not true. [1] CP/M 3 (normally called "CP/M Plus") does not have or support subdirectories, only user areas, just the same as earlier versions... (Such as B4:MYFILE.TXT or A0:WORDSTAR.COM.) Source: me -- I own 2 CP/M 3 computers. Feel free to check the manual: http://www.bitsavers.org/pdf/digitalResearch/cpm_plus/CPM-Plus_Users_Guide_Prelim_Nov82.pdf http://www.bitsavers.org/pdf/digitalResearch/cpm_plus/CPM-Pl... [2] CP/M does not have standard command line switches or arguments, so there is no standard delimiter.
- fanf2 3y agoI used to believe that too, but https://lobste.rs/s/rar1ec/rust_security_advisory_for_standard#c_mfa0o8 https://lobste.rs/s/rar1ec/rust_security_advisory_for_standa... I looked at some CP/M manuals from around 1980 and the commands mostly did not have options. The closest was PIP which put options inside [ ] and there was no / nor \ to be seen.
- lproven 3y agoFalse. Not true, never was. Here's the real story: https://www.os2museum.com/wp/why-does-windows-really-use-backslash-as-path-separator/ https://www.os2museum.com/wp/why-does-windows-really-use-bac...