https://gitlab.synchro.net/main/sbbs/-/commit/1917099ba9f7dabd7940a2a7fd8de7dff1929aed#note_4742

@rswindell Will this work on Windows? Windows uses backslashes (\) to separate directories. I thought it would be standard practice to use backslash() to ensure the path has the correct slash in it?
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/1917099ba9f7dabd7940a2a7fd8de7dff1929aed#note_4743

Forward slash works just fine in Windows. See `exec/*.js` for plenty of examples of this use.

A backslash is only important when the path might be passed to external program, and that conversion happens automatically by Synchronet, when necessary (and only on Windows).

So use a forward slash in paths.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/1917099ba9f7dabd7940a2a7fd8de7dff1929aed#note_4744

Is there a reason to use backslash() then? Is backslash() deprecated?
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/1917099ba9f7dabd7940a2a7fd8de7dff1929aed#note_4745

backslash() is for appending a slash or backslash on the end of a string when you're going to possibly pass that string onto an OS path interpreter (e.g. command.com, cmd.exe) where it then matters if it's a backward or forward slash (on Windows).

backslash() is not deprecated is sometimes necessary, like I said, when you're passing the resulting string on to an external program.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)