4 ms·
BANCStar was never intended as a programming language, rather as a bytecode for a programming language VM. What happened though, is the vendor shipped the produ
by skissane 5y ago
BANCStar was never intended as a programming language, rather as a bytecode for a programming language VM. What happened though, is the vendor shipped the product to customers, some customers found the VM and started writing code for it directly, which the vendor never intended them to do. That is why it was such an awful programming language - it was never meant to be used as one. Imagine if people wrote JVM bytecode directly, without even using assembler mnemonics - that would be equivalent to BANCStar.
If the customers were more skilled, they would have written a disassembler/assembler to convert it to more reasonable syntax. This is the kind of thing that “too smart by half” people do - smart enough to rip off the covers and start tinkering with the internals, not smart enough to build some tools to make it easier for themselves. (It appears some of them eventually did do that, but others just stuck with writing the stuff by hand.)
- WalterBright 5y agoThe general progression is one writes: 1. machine code 2. assembler 3. macro assembler 4. high level language At each stage, the effort required to produce the tool is justified by increasing usage of the machine.
- mst 5y agoI wonder how viable it was to write it by hand and still be able to use the editor to modify the simpler parts of the file. "Not being able to mix and match" has always been where I've got stuck (from both directions before now) with other environments.
- AzzieElbab 5y agoI think it was pretty valuable to people who did write bancstar by hand. The value came from either job security or consulting fees