Talk:Turbo Assembler

Latest comment: 11 months ago by 84.158.122.223 in topic Version history missing

To merge

edit

The following has been moved from the former TASM article (now a #redirect here) relevant parts are to be merged into this article. --Wernher 30 Nov 2004 0500 (UTC)

TASM or Turbo Assembler, is the assembler product from Borland. It converts assembly language code to machine code.

Rise of TASM

edit

TASM gained popularity with developers who used Borland's Turbo Pascal, Turbo C, Turbo C++ and Borland C++ products. Like its siblings, TASM was known to be fast and efficient.

We're talking about a time when programming for the PC hardware platform meant, many a times, having to resort to programming in assembly language for performance. During those times, Borland was well known for products that were far superior to those from Microsoft.

TASM simplifies assembly language programming

edit

MASM, the Macro Assembler from Microsoft, was a complicated beast to deal with mainly due to the assembler directives and error prone data type handling. TASM simplified assembler directives and helped boost the productivity of programmers (the last thing you want to break your head about when programming in assembly is assembler directives) - this was done by the introduction of what Borland called "IDEAL mode". TASM also provided a compatibility mode for legacy code written for MASM. With additional features like structured record handling and stricter data type checking TASM was the ideal choice for many.

Who uses TASM today?

edit

I'm really not sure, since TASM does not seem to be available beyond Borland C++ Builder 5. Even if it were available, only some people would use it, probably in the world of embedded systems or operating systems, where assembly language is sometimes the (only and) best way to implement things.

The architecture of modern x86 microprocessors, like the Pentium or the processors from AMD, actually makes writing assembly language code inefficient in many cases. Good and efficient code generation in many cases is best left to high level language optimizing compilers that can analyze the code flow far better than a human can, taking into consideration issues like pipelining, branching, register usage etc.

Some use it in the retro scene to write software for old x86 CPUs. --84.158.122.223 (talk) 18:51, 19 November 2023 (UTC)Reply

TASM Still Sold

edit

If TASM isn't being actively maintained, it's still being sold commercially by Borland. See: http://www.borland.com/us/products/classic_products/index.html. This should be mentioned in the article, as it gives the impression TASM is abandonware.

As of 2015, this is no longer the case (link invalid, search of site invalid). --Trixter (talk) 17:42, 12 March 2015 (UTC)Reply

Current Development

edit

TASM is still bundled with Embarcadero C++ Builder and Delphi products. The current version (shipping with 2010 versioned products) is 5.4, Copyright 2009 to Codegear. Therefore, the statement that TASM is no longer maintained is inaccurate. —Preceding unsigned comment added by 121.44.208.227 (talk) 09:53, 28 July 2010 (UTC)Reply

Unfortunately, Embarcadero's version 5.4 (4 November 2010) is virtually identical to Inprise's version 5.3 (30 May 2000) with the name of the company changed. Even the file sizes of the 5.3 and 5.4 are the same (188416 bytes). What was new in version 5.3 was the added MMX support. And nothing has changed since. By contrast, MASM version 6.15, dated 2 months earlier than TASM version 5.3, already supported not just MMX, but also 3DNow! and SSE. So, already in 2000 TASM lagged behind, and since then it has no longer really been developed... Лъчезар共产主义万岁 10:31, 10 September 2011 (UTC)Reply

Informal tone

edit

Doesn't this article have a bit of an informal tone to it, not exactly becoming of an encyclopedia? — Preceding unsigned comment added by 212.77.163.111 (talk) 08:11, 16 January 2015 (UTC)Reply

Yes. I removed some content not appropriate for the article and not directly related to TA. The assembly example is also too verbose and not properly indented; this should be addressed at some point. --Trixter (talk) 17:41, 12 March 2015 (UTC)Reply
Fixed the example assembly code which was a complete joke.

Version history missing

edit

A version history is missing. And from which version was TASM extender included? 84.158.122.223 (talk) 18:52, 19 November 2023 (UTC)Reply