CBASIC

In the world of CBASIC, there has always been a constant and ever-evolving interest. Whether we are talking about a historical figure, a cultural phenomenon or a scientific topic, CBASIC has left its mark on humanity in one way or another. Its influence has spread over time and continues to impact today. In this article, we will closely explore the importance of CBASIC and how it has shaped our society, as well as the implications it has for the future. From its beginnings to the present, CBASIC has generated countless discussions, debates and studies that seek to understand its scope and meaning in people's lives.

CBASIC
The workflow of compiler and interpreter
DeveloperGordon Eubanks
First appeared1976 (1976)
Implementation languagePL/M
OSCP/M

CBASIC is a compiled version of the BASIC programming language written for the CP/M operating system by Gordon Eubanks in 1976–1977. It is an enhanced version of BASIC-E.[1][2]

History

BASIC-E was Eubank's master's thesis project.[1][2] It was developed in PL/M by Eubanks for Gary Kildall's new CP/M operating system while both men were at the Naval Postgraduate School in Monterey, California.[1][2] BASIC-E was based on a BASIC compiler originally written by Gary Kildall in 1974.[1][2]

Because it was developed at public expense, BASIC-E is in the public domain and cannot be marketed exclusively.[1][2][3] Seymour Rubinstein, the marketing director of IMSAI contacted Eubanks and asked him to create a saleable version under contract for the IMSAI 8080 microcomputer.[4] Eubanks developed CBASIC in his spare time while he was still a naval officer stationed on the submarine USS George Washington at Vallejo, California. He retained joint ownership of the program with IMSAI, and sold the program through his own company, Compiler Systems, until it was acquired by Digital Research[1][2] in 1981.

  • CBASIC COMPILER VER 2.07
  • CRUN VER 2.38 / COPYRIGHT 1981 COMPILER SYSTEMS INC.

Features

BASIC-E and early versions of CBASIC compiled source code into an intermediate p-code file, which was then executed by a separate run-time interpreter program. CBASIC could execute in a minimum of 24 KB of memory. Line numbers in the program source were optional, unless needed as a label for a program jump. CBASIC proved very popular because it incorporated 14-digit binary-coded decimal (BCD) math which eliminated MBASIC's rounding errors that were sometimes troublesome for accounting.

CBASIC2 adds the following features:

  • Integer variables
  • Chaining with common variables
  • Additional pre-defined functions
  • Cross reference capability

Reception

InfoWorld in 1980 described CBASIC as the "primary language for the development of commercial CP/M applications", because of developers' widespread familiarity with BASIC and ability to distribute royalty-free binaries without source code to CBASIC owners. The magazine stated that the language had become popular "despite serious drawbacks", including the required preprocessor for interpreted source code making debugging difficult, slow speed, and incompatible changes.[5] Jerry Pournelle said in May 1983 that Digital Research had "practically ruin" Eubanks' CBASIC manual after acquiring his company, but that the new edition was much better.[6]

References

  1. ^ a b c d e f Shustek, Len (August 2, 2016). "In His Own Words: Gary Kildall". Remarkable People. Computer History Museum.
  2. ^ a b c d e f Kildall, Gary Arlen (August 2, 2016) . Kildall, Scott; Kildall, Kristin (eds.). "Computer Connections: People, Places, and Events in the Evolution of the Personal Computer Industry" (Manuscript, part 1). Kildall Family. Retrieved November 17, 2016.
  3. ^ CPM User Group The source code can be found on Volume 30
  4. ^ Gordon Eubanks oral history transcript Archived August 24, 2006, at the Wayback Machine p. 9, November 2000, Computerworld Honors Program
  5. ^ "Editorial". InfoWorld. Vol. 2, no. 15. August 18, 1980. p. 8.
  6. ^ Pournelle, Jerry (May 1983). "Ulterior Motives, Lobo, Buying Your First Computer, JRT Update". BYTE. Vol. 8, no. 5. pp. 298–324.