Are you writing custom VBA functions and macros in Excel?
If he is, that's programming by any stretch of the imagination.
By the way, thanks to y'all, there are now two new keywords in TBL: .HEXIFY, as described earlier, and .ATTACH, mostly to handle the results from .HEXIFY more intuitively.
So you could do (excerpt here):
Code:
.ROLL <2d6>
.HEXIFY {$Roll} TO {HexTemp}
.ATTACH {HexTemp} AFTER {HexString}
At the moment the first argument after .ATTACH
must be a variable because I just wanted to get the command in there. At some point I'll set it up to handle complete strings, too, like the predicate of a .JOIN command.
I definitely need less caffeine or more sleep; now I'm wondering if there's any use for octal values in TableMaster ... aside from random TOPS-10 PPNs, I can't think of any application.
Okay, I feel old ... I can't remember my current phone number without thinking about it ... I can't remember my mother's phone number at all without looking it up ... but I remember my CompuServe login PPN *and* password from 20+ years ago. There's something a bit disturbing about that.
Speaking of things that are programming languages but don't look like it ... who here remembers TECO from back in the DEC days? Among the stranger things I've ever encountered was an implementation of ELIZA written in TECO. Not by me, mind you -- I never used the thing for anything more than editing, and not even that once I got my hands on EDT. (my fingers could probably remember the EDT keypad commands by muscle memory) But theoretically you could do anything in TECO ... and probably had to. I've been told that EMACS started its life as a bunch of TECO macros, and I'd believe it. They're both cryptic, incomprehensible, complicated, and make me swear.
Another reason I feel old: remembering the days before full-screen editors. (and they're not good memories)
Rambling down memory lane again, the first incarnation of TableMaster had a debug mode (conditional compilation) where it would dump out the contents of the insanely complicated mess of linked lists that held the table data. The old Turbo Pascal, that came on a 5.25" floppy, didn't have anything like a debugger; that was the only way to see what was going on in there. When I upgraded to Borland Pascal, it had a debugger but it was such a pain to use I stayed with my existing print statements. Ah, the good old days ... they were terrible.
Any time I have a lingering trace of nostalgia, I remember those print statements, and laying out yards of fanfold printouts on a table and marking them up with multi-colored highlighters. I'll keep my nostalgia for my vintage postcard collection; when it comes to software, I'm happy to be rid of it.