palordrolap

There used to be an undocumented setting in early versions of MS-DOS that would allow the setting of the command option character to something other than the slash, and if you did that, the slash automatically became the path separator. All you needed was SWITCHAR=- in your CONFIG.SYS and DOS was suddenly very Unix-y.

It was taken out after a while because, with the feature being undocumented, too many people didn’t know about it and bits of software - especially batch files, would have been reliant on things being “wrong”. The modern support for regular slash in API calls probably doesn’t use any of the old SWITCHAR code, but it is, in some way, the spiritual descendant of that secret feature.

Here’s an old blog that talks about it: https://learn.microsoft.com/en-gb/archive/blogs/larryosterman/why-is-the-dos-path-character

Given the engineer’s amendment to “If it ain’t broke, don’t fix it.” is usually “If it ain’t broke, it doesn’t have enough features yet.”, I can only surmise that COBOL must be one of those languages that are so terrible that they deter their programmers from wanting to do that.

Urge to analyse… rising…

My first guess would be to take out that semicolon on line 264. JavaScript will often happily take a new line as end of statement if it makes sense to do that, so in theory, that semicolon is not needed. And it might be a Greek question mark your prankster colleague put in your code when you weren’t looking.

And then I’d be tracing parentheses, curlies, quotes and so on, because that error could be the point the parser gave up trying to make sense of the code rather than where the error actually is.

And if that didn’t find it, I’d put in a deliberate error at an earlier, known line to see where the parser thinks that error is. If it’s offset by 20 lines, then I know the original error is probably offset by a similar amount.

Ah, misleading use of terminology that indicates one thing, but will win in court even if it actually means, or can later be said to mean, another.

I hope those involved in helping companies win these lawsuits choke on bones from food sold as boneless. Because that won a court case after “boneless” was redefined as a cooking method.

I don’t want them to choke to death. Just a little lesson, you know?

Sometimes, programs that need to start up an editor will honour the $EDITOR environment variable, which should contain the name of, or full path to, a user’s preferred editor.

It’s not set by default though, and a lot of things will naturally default to vi or even ed. Something to be set in a .profile, .bashrc or similar.

$VISUAL is another variable that is used for similar purposes.

The resemblance to certain two letter commands is not entirely a coincidence.