GFA BASIC is a dialect of the BASICprogramming language, by Frank Ostrowski. The name is derived from the company ("GFA Systemtechnik GmbH"), which distributed the software. In the mid-1980s to the 1990s it enjoyed popularity as an advanced BASIC dialect, but has been mostly superseded by several other programming languages. Official support ended in the begin of 2000s.

Contents

GFA BASIC was developed by Frank Ostrowski at "GFA Systemtechnik GmbH" (later "GFA Software"), a German company in Kiel and Düsseldorf. GFA is an acronym for "Gesellschaft für Automatisierung" ("Company for Automation"), which gave name to the software. The first GFA BASIC version was released in 1986. In the mid and late 1980s it became very popular for the Atari ST home computer range, since the Atari ST BASIC shipped with them was more primitive. Later, ports for the Commodore Amiga, DOS and Windows were marketed. Version 2.0 was the most popular release of GFA BASIC as it offered then many more advanced features compared to alternatives. GFA BASIC 3.0 included further improvements like support for user-defined structures and other agglomerated data types. The final released version was 3.6. Around 2002 GFA software ceased all GFA BASIC activities and shut down the mailinglist and website in 2005.[1] Due to missing official support and availability of GFA BASIC the user community took over the support and an installed an own communication infrastructure.[2][3]

As of version 2.0, the most popular release, GFA BASIC was a very modern programming language for its time. Line numbers were not used and one line was equivalent to one command. To greatly simplify maintenance of long listings, the IDE even allowed for code folding. It had a reasonable range of structured programming commands — procedures with local variables and parameter passing by value or reference, loop constructs, etc. Modularization was only rudimentary, making GFA BASIC 2.0 best suited for small and medium-sized projects.

The GFA BASIC interpreter is compact and reasonably fast, and was shipped with a runtime that could be distributed freely with one's programs. When a compiler was made available, execution speed could be increased by approximately a factor of 2. GFA BASIC allowed extreme optimisations for execution speed, supporting some direct assembler-level calls, and even the ability to embed sections of assembler code directly within the BASIC source code. GFA BASIC integrated neatly into GEM and TOS, the Atari ST's operating system, providing menus, dialog boxes, and mouse control. (See WIMP interface.)

Although the source code was usually stored in a tokenized version to save room on disk, pieces of code could also be saved in ASCII form, and as such made it possible to set up reusable libraries. The tokenized source files were a benefit in other ways too — for instance, GFA BASIC allowed users to include binary data in their BASIC code via an "INLINE" statement, and could even be integrated with the GFA Assembler to allow users to develop machine code programs inside INLINE statements in order to accelerate particular areas of a program. It also meant that the BASIC interpreter (and later the compiler) didn't need to tokenise a program when it was loaded, which would have been a significant load-time overhead for some of the larger GFA BASIC programs that were written.

The Atari ST had an enthusiastic user base in Germany, GFA's home market. The strength of this local market helped to encourage a number of German companies to develop sophisticated technically oriented tools and applications for the ST, such as Calamus, an advanced desktop publishing system almost unknown outside of Germany.

Many Atari ST users were introduced to GFA BASIC through magazine articles and tutorials in popular Atari magazines, such as ST Format, and free copies were sometimes given away on these magazines' cover discs.

GFA BASIC for DOS allowed users to write programs that would run under DOS with crude Windows-like GUI interface support. This was useful for writing utilities for low-level disc operations, without the user being restricted to a command-line interface. Porting a GFA program to DOS usually required changing colour values to match the DOS system pallette.

GFA BASIC for Microsoft Windows included a thorough implementation of the Windows API calls. Although the product had a number of technical advantages over some of the more popular products (the combination of an "easy" language with robust architecture and fast, compiled, reliable code), it didn't achieve great success in the Windows market. Software professionals who wanted high-performance code tended to stay with the more "technical" languages, and to regard BASICs as inferior. For professionals who didn't have a problem with BASIC, a number of well-established software tool vendors such as Microsoft and Borland were actively promoting new "visual" programming systems such as Visual Basic. These allowed users to create windows and dialog boxes populated by standard components (text, buttons, frame outlines) with the help of a drag-and-drop interface and object-oriented editing.

One of the advantages of GFA BASIC for Windows was that the compiler (sold separately) could create stand-alone .exe files, and also included a relatively easy option for creating Dynamic Link Library (.DLL) files for Windows. This allowed a user to write and test routines within GFA Basic, export them as functions to a Windows .DLL file, and then access those pre-compiled functions from within other tools or programs, such as Visual Basic 3.0, which was unable to produce compiled code. This feature allowed GFA BASIC to be used as a "number-crunching" add-on product for Visual Basic, for writing high-speed routines for applications such as database sorting or media signal processing that would have been impractical under the then-current version of Visual Basic.

GFA BASIC did not have the company recognition or product recognition factors of companies such as Microsoft and Borland in the United States market, and as a simple text-based code creation system, it lacked the exciting new "visual" user interfaces of its better-known competitors. Although GFA BASIC for Windows was developed further to include support for Visual Basic's components, their use under GFA was more technical than under Visual Basic. Without a large marketing budget, or a clear reason why journalists should write about it, GFA BASIC for Windows remained a comparatively obscure product.

GFA Basic was widely used to quickly create editors by game developers. For example, Éric Chahi wrote a game editor in GFA basic to create his game Another World, including scene design and game scripting; only the game engine (polygon rendering and music) was done in assembler. This editor was used to make all ports of the game, including for consoles and the Collector Edition for Windows released in 2006.[4] Similarly, Karsten Köper of Thalion software wrote all the basic game editing software for the "Amberstar" series using GFA Basic.

In a time before document scanners and online help, some editions of the GFA manual were printed with black ink on red paper, in an attempt to thwart photocopying and bootlegging. The effectiveness of this tactic was questionable,[5] and the manual returned to the usual black-on-white format after complaints from colour blind users and the proliferation of re-typed copies on the Internet.

^Another World Édition Spéciale 15ème Anniversaire for Windows, included making-of. Released by ElektroGames and SdLL (2006).

^"GFA Basic Compiler". Another point is that it has been printed on a bright red paper, a technique used to stop photocopying. I tested this and found that with a bit of experimentation, the photocopy was easier to read than the original manual!