11–20 of 60 posts
In page 44 onwards, this describes how to do class-based OOP with assembly language extensions to generate vtable calls. I wonder who ever used that…
Borland C++ 3.1 was the epitome of documentation. The retail packaging was about the width of 7 pieces of big box software and it weighed quite a bit more from the "encyclopedia set" it included. The assembler quick reference guide for TASM was better in 3.1 than in either 4 or 5. It was also spiral bound with a white comb. Although updated with features, 4 and 5 reduced the amount of documentation significantly.
Borland manuals were a pure delight.. as was the speed of Turbo Pascal compilation and the elegance of their text mode windowing object system. I remember scouring all the possible BBS dialup file servers to find a compiler for my first 8086 machine .. I knew there had to be something better than GW Basic .. I could not find a compiler for free, but did happen up on A86 assembler, so got an intro to how the machine r…
However when I could afford the student editions of Borland products available to high school students, I bought TPW and Turbo C++ 3.1 for Windows, first TPW, and then TC++ an year later.
My favourite Assembler, in those days I would imagine Assembly would be the way to keep coding going forward, how wrong I was.
Scrolling through it just now, I now also remember "Ideal" mode, and how it was so much better than MASMs weird idiosyncrasies.
[edit]..and run it on dosbox-x or 86box, of course.
Borland manuals were a pure delight.. as was the speed of Turbo Pascal compilation and the elegance of their text mode windowing object system. I remember scouring all the possible BBS dialup file servers to find a compiler for my first 8086 machine .. I knew there had to be something better than GW Basic .. I could not find a compiler for free, but did happen up on A86 assembler, so got an intro to how the machine r…
I got pirated Turbo Pascal 7 and Turbo Basic with included manuals and I've learned programming from them (in a foreign language, with no internet).
That's how good they were.
http://bitsavers.informatik.uni-stuttgart.de/pdf/borland/tur... Turbo C 2.0 user manual from the same site - it is just a gold mine.
In VS today everything feels so cumbersome and convoluted I almost never bother witht the debugger, and instead just look at stack traces instead.