I have to go back to around 1992 or so for this one ... not that I don't have plenty of newer humbling learning moments, but this is the one I tend to think of as the most obvious "how did I do all of these things without knowing something so basic."
Background: I was in the 7th grade, hosting a BBS and wanted to simultaneously host two different BBSes behind the same modem (and both with a working FIDO feed). I can't remember specifically why, but it had something to do with how one of the two BBS systems detected if it should ingest messages or if it should return a user session. I believe I was handling that detection manually but still had to have the BBS setup in such a way that it would look for a specific exit code from FIDO and if it saw "0" (which was what it always saw in this configuration), it never provided a user session in response.
Let's start with the first problem. I had a non-working understanding of what an exit code actually was. This was all-together weird. I'm in 7th grade, but I'm taking AP Computer Science at the High School. I mean, I think by then I could actually make Wing Commander start or some equally heroic juggling of HIMEM statements with the various TSRs. I was writing actual software in Borland Turbo Pascal 4, compiled to an executable file, every one of which returned an exit code. I'm fairly certain the last statement of many of my programs was something along the lines of "RETURN 0;" if memory serves. I had even processed command-line arguments at this point!
In what easily made me look like the 7th-grader that I was, I called another programmer I had met on a local BBS (after 10:00 PM, no internet, long distance was expensive) who was writing a BBS application in "C" ... and asked him if he had any time that week to write me a quick program which took, as a parameter, any number 0-255 and exited with that exit code. You can't imagine how thankful I was when he was uploading the program to my second node before we had finished talking.
You can't imagine how stupid I felt when I found the seven hundred other ways this could be done, including with a BATCH file, that I had just never had any real reason, up to that point, to properly connect with the words "exit code" (it was an ERRORLEVEL, you could set it directly (?) in DOS).
Background: I was in the 7th grade, hosting a BBS and wanted to simultaneously host two different BBSes behind the same modem (and both with a working FIDO feed). I can't remember specifically why, but it had something to do with how one of the two BBS systems detected if it should ingest messages or if it should return a user session. I believe I was handling that detection manually but still had to have the BBS setup in such a way that it would look for a specific exit code from FIDO and if it saw "0" (which was what it always saw in this configuration), it never provided a user session in response.
Let's start with the first problem. I had a non-working understanding of what an exit code actually was. This was all-together weird. I'm in 7th grade, but I'm taking AP Computer Science at the High School. I mean, I think by then I could actually make Wing Commander start or some equally heroic juggling of HIMEM statements with the various TSRs. I was writing actual software in Borland Turbo Pascal 4, compiled to an executable file, every one of which returned an exit code. I'm fairly certain the last statement of many of my programs was something along the lines of "RETURN 0;" if memory serves. I had even processed command-line arguments at this point!
In what easily made me look like the 7th-grader that I was, I called another programmer I had met on a local BBS (after 10:00 PM, no internet, long distance was expensive) who was writing a BBS application in "C" ... and asked him if he had any time that week to write me a quick program which took, as a parameter, any number 0-255 and exited with that exit code. You can't imagine how thankful I was when he was uploading the program to my second node before we had finished talking.
You can't imagine how stupid I felt when I found the seven hundred other ways this could be done, including with a BATCH file, that I had just never had any real reason, up to that point, to properly connect with the words "exit code" (it was an ERRORLEVEL, you could set it directly (?) in DOS).