7 ms·
Borland Turbo Assembler Version 5 User's Guide (1996) [pdf]
- pjmlp 4y agoMy favourite Assembler, in those days I would imagine Assembly would be the way to keep coding going forward, how wrong I was.
- mhd 4y agoA friend of mine used to be a big proponent of this. His theory being that sure, you need someone special to be very productive in assembly. But there's a billion of Chinese where the market is just opening up… (So I guess it was a few assembly geniuses for your OS and productivity software and the rest of us mortals filling in with the less performant rest written in C++ or E or Blitz Basic something)
- anta40 4y agoI discovered Randall Hyde's HLA (High Level Assembly) while in the university around 2005/2006: https://www.plantation-productions.com/Webster/HighLevelAsm/index.html https://www.plantation-productions.com/Webster/HighLevelAsm/... and thought it would be awesome to use that for work. Imagine the power of assembly combined with readability/productivity like Pascal. Well, I never use assembly professionally, and HLA itself isn't maintained anymore.
- pjmlp 4y agoMASM is still maintained, which is even more high level than TASM was. But yeah, other than some weekend hacks not worth the trouble.
- a1369209993 4y agoErratum on the off chance anyone relevant is reading here: page i and ii (first two pages of the table of contents) are in the wrong order (swapped).
- msravi 4y agoBrings back fond memories. Used to use the "debug" program that came with DOS to play with assembly as a student, because TASM (Borland) and MASM (Microsoft) cost money, but doing that gave one a real feel for assembly. Coding a short JMP instruction, for example, requires a relative address from the current instruction PC, so you had to hand compute that and code it in. And if you added instructions between the JMP and the target, then you had to go back and change it.
- jstgord 4y agoBorland 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 really worked. Was so happy when I could afford Turbo Pascal back in the day. best product ever.
- pjmlp 4y agoMe too, like as it used to be in those days, we could get all kinds of software in Portuguese bazars at the cost of the material being copied. 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.
- ajuc 4y agoI was 14 years old, only ever programmed in Commodore Basic by typing in programs from the manual (in German) without understanding them, didn't understood English much. 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.
- elvis70 4y ago
- limmeau 4y agoIn 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…
- varjag 4y agoWe used it for the kicks at the Uni. Never got to try that in prod because frankly the next time it came to using assembler it was 15 years later (and on another arch).
- aforwardslash 4y agoWhen I was a teen, I used TA precisely because of oop support :) it was a bit cumberstone compared to higher level languages, but worked quite well for the kind of stuff I needed (mostly display-related and IO libraries)
- bzzzt 4y agoOOP hype was peaking in the mid-90's when TASM 5 came out. Probably some manager's idea to capitalise on that.
- dalf 4y agoThis helped to understand how OOP was working under the hood (I was a teen at that time) This post brings me many memories from Turbo Vision, Borland Graphics Interface, a simple assembly language, the flat memory hack, Turbo Pascal with its super fast compile time...
- pfoof 4y ago>Most people think of assembly language as a low-level language. Turbo Assembler, however, provides many of the features of a high-level language (such as abstract data types, and easy interfacing to other languages). The addition of object-oriented data structures gives Turbo Assembler the power to create object-oriented programs as easily as high-level languages while retaining- the speed and flexibility of assembly language. Shocking and surprising
- dools 4y agoI actually found something similar in PIC micro controller assembly at uni. The way library loading worked allowed something very similar to object orientation in a super fast assembly language. My team wrote our 3rd year project in assembly and found that we experienced far fewer WTF moments and unexpected behaviours than all the other teams who chose to use C.
- pfoof 4y agoSimilar to my uni project to make a concurrent server. Most people struggled to make it work with Java, and there were extra points for implementation of the project in C. So I did. Pthreads, zero deadlocks and zero memory leaks.
- zwieback 4y agoI remember coming across that - we mostly used MASM back in the day but when I found the object-oriented TASM stuff I was very tempted. Didn't really make a whole lot of sense since C++ is already pretty low-level, especially back in the 90s. The other interesting Borland OO thing was the C++ language extension for OWL (Object Windows Library, an early C++ GUI lib for WIndows) to link windows messages to member functions. It was addictively productive, when we switched over to MFC later on it felt like a step back.
- mistrial9 4y agoI wrote C code with dispatch tables to implement "virtual functions" for structs with method calls .. those were local to a dot-c file, with corresponding external dot-h interfaces defined.. all of that by my own design, for a framework for graphics programming .. in the early 90s. The techniques were known, just not common. Borland had great products, and was killed by "bloody means", by MSFT, in public view.
- 1letterunixname 4y agoBorland 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.
- pjmlp 4y agoAll Turbo Pascal editions up to TPW 1.5 also had plenty of nice manuals, and in similar number.
- tengwar2 4y agoI'm not sure if it was that one, but there was one edition of Borland C++ which had a handle on the top of the box containing the manuals, and a safety warning about lifting carefully.
- dis-sys 4y agohttp://bitsavers.informatik.uni-stuttgart.de/pdf/borland/turbo_c/Turbo_C_User_Guide_Ver_2.0_1988.pdf 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.
- actionfromafar 4y agoI don't understand - the debugger in Turbo C was such a delight and inspecting structs, linked lists etc was so easy and somehow fit nicely on these old screens. In VS today everything feels so cumbersome and convoluted I almost never bother witht the debugger, and instead just look at stack traces instead.
- pjmlp 4y agoAs Borland fanboy that used most of their products until early 2000's, and nowadays lives on VS, I fail to see what is actually missing.
- anyfoo 4y agoAh, I had TASM 5, boxed. Great memories. I actually remember reading the manual for fun. If I remember right there were two manuals in the box, this one and an assembly reference. Scrolling through it just now, I now also remember "Ideal" mode, and how it was so much better than MASMs weird idiosyncrasies.
- rnd0 4y agoHopefully everyone's noticed there's a ton of Borland manuals at Bitsavers, not just TASM v5. You could probably even pick up the software itself if you wanted maybe off of archive.org? [edit]..and run it on dosbox-x or 86box, of course.
- golem14 4y agoSad to see how crappy today’s assembler documentation is in comparison (especially Apple)
- DominoTree 4y agoWorth pointing out that in the late 80s-early 90s, Turbo C and Turbo Pascal, and maybe others, were also licensed and ported to the (M68K-based) Atari ST as “Pure C” and so forth - and worked just as well there, including some of the best online documentation of anything ever written for the platform
- dark-star 4y agoI still have the Turbo Debugger 2.0 manual in my bookshelf...
- nurettin 4y agoAs a kid who was left alone with a computer for way too long back in the early 90s, I remember learning English from Civilopedia and playing around with Borland turbo pascal 7. TP manual had an example where they built polynomials using linked lists. That was the first time I realized that you could store pointers to other regions of memory which store pointers. Nobody around me had any clue why I was so happy.
- tamaharbor 4y agoI still use Turbo Basic.
- miohtama 4y agoFrom the era when software development still had documentation, and technical writers.
- DefNotMe 4y agoMy school teaches C++ on TC++ 3.1, The syllabus for CS hasn't changed since about 20 years. 80586 Pentium is still cutting edge in there.
- myth_drannon 4y agoIs it in India? I was buffled when I found a lot of recent Youtube videos teaching Turbo C. Then realized all of them were Indian and for Indian students.
- pjmlp 4y agoYeah, on one side we are trying to preach modern practices how to program in C++, and then we get these schools teaching pre-standard C++ for a dead OS.
- dwringer 4y agoI encountered this about 10 years ago here in the US. The course seemed to have become a kind of Kobayashi Maru - nobody else in my group ever even managed to get a working installation of the compiler, which we had to do in a Windows XP VM (there was some way of getting a license for a copy of XP but almost nobody in the class seemed to get it to work for some reason).
- ihatepython 4y agoPersonally I don't believe in the no-win situation
- VikingCoder 4y agoI learned programming by reading Borland's manuals. I owe their writers a debt of gratitude.
- atombender 4y agoBorland's manuals were fantastic in so many ways, from the typesetting to the organization of the chapters/books. They were, in comparison to many other manuals, both friendly and pragmatic. Look at the "Getting started" part of this manual. The marketing copy is top notch (referencing "hackers and wizards", "blindingly fast programs"), and then just one page later you're running your first program. One of the formative experiences of my childhood was getting my hands on the Turbo Pascal 5.5 "Object-Oriented Programming Guide" (1989) [1] just before going on a ferry holiday to Germany. It was a relatively slim volume that was separate from the other manuals that came with TP. On that ferry trip I read the book cover to cover, and even started writing programs on paper, since I didn't have a computer with me. I had learned procedural programming before then, and Pascal's OOP extensions just blew my mind at the time. Looking at the manual now, it's just really well written and laid out. [1] http://www.bitsavers.org/pdf/borland/turbo_pascal/Turbo_Pascal_Version_5.5_Object-Oriented_Programming_Guide_1989.pdf http://www.bitsavers.org/pdf/borland/turbo_pascal/Turbo_Pasc...