Jump to content

TRAC (programming language)

From Wikipedia, the free encyclopedia
(Redirected from TRAC programming language)
TRAC
Paradigmgeneral-purpose macro processor
Designed byCalvin Mooers
First appeared1964
Stable release
T2001[1] / November 17, 2001; 23 years ago (2001-11-17) [2]
Influenced by
Macro SAP[3]
Influenced
SAM76, ML/I[3]

TRAC (for Text Reckoning And Compiling) Language is a programming language developed between 1959–1964 by Calvin Mooers and first implemented on the PDP-1 in 1964 by L. Peter Deutsch.[4] It was one of three "first languages" recommended by Ted Nelson in Computer Lib. TRAC T64 was used until at least 1984, when Mooers updated it to TRAC T84.[4]

Language description

[edit]

TRAC is a purely text-based language — a kind of macro language. Unlike traditional ad hoc macro languages of the time, such as those found in assemblers, TRAC is well planned, consistent, and in many senses complete[fact or opinion?]. It has explicit input and output operators, unlike the typical implicit I/O at the outermost macro level, which makes it simultaneously simpler and more versatile[vague] than older macro languages.

TRAC is a text-processing language,[5] also called a string processing language.[6] Because of this the only data type available is a string of characters. Numbers are strings of digits, with integer arithmetic (without specific limits on maximum values) being provided through built-in ("primitive") functions which operate on their string representation. Arguably, one aspect of its completeness is that the concept of an error is limited to events like lack of file space and requesting expansion of a string longer than the interpreter's working storage; what would in many languages be described as illegal operations are dealt with in TRAC by defining a result (often a null string) for every possible combination of a function's argument strings.

TRAC is, like APL or LISP, an expression oriented language (in contrast to more typical procedure-oriented languages) but, unlike APL, it completely lacks operators. In most respects, it is a case of pure functional programming. It has, in common with LISP, a syntax that generally involves the presence of many levels of nested parentheses.

TRAC is homoiconic: that is, a TRAC program can be represented and manipulated within the TRAC language itself.[7][8][9] The emphasis on strings as the single data type is so strong that TRAC provides mechanisms for handling the language's own syntactic characters either in their syntactic roles or like any other character, and self-modifying code has more the feel of a natural consequence of typical TRAC programming techniques than of being a special feature.

The main inspiration for TRAC came from three papers by Douglas McIlroy.[7][10][11][12]

Intellectual property

[edit]

Mooers trademarked the name TRAC in an effort to maintain his control over the definition of the language, an unusual and pioneering action at the time. At one point, he brought an intellectual property infringement suit against DEC, alleging that a contract to deliver a mini-computer with a TRAC interpreter violated his rights. "The first issue of Dr. Dobb's Journal, one of the early publications in the personal computer field, has a vitriolic editorial against Mooers and his rapacity in trying to charge people for his computing language."[13][14] The name has since been used several times for unrelated information technology projects, including a current open source project management system called Trac.

Influence and usage

[edit]

TRAC was later implemented on the PDP-8, PDP-10, and PDP-11.

There have been various languages inspired by TRAC. To avoid any trouble with Mooers, they renamed primitives and/or used different metacharacters. In SAM76's case, primitives were added, according to Claude Kagan, "because TRAC is baby talk". In MINT's case, primitives were added to give access to a sophisticated text editor machinery.

  • one perceived shortcoming of TRAC was lack of full extensibility: some TRAC primitive functions are sensitive to the distinction between a null (zero-character) argument and a nonexistent (non-delimited) one, but beyond its last non-null argument, a user-defined function cannot make the distinction. SAM76 was a TRAC-like language which eliminated that limitation.
  • Russ Nelson implemented an emacs extension language named MINT (MINT Is Not TRAC). This language is used by the FreeDOS editor FreeMACS.
  • John Walker implemented an embeddable extension language library DIESEL [15] (Dumb Interpretively Evaluated String Expression Language) originally for menu macro processing in AutoCAD.[16]

TRAC was used by FTP Software in its PC/TCP product as the modem dialer scripting language.

TRAC was also used as a front end on Digital Productions Cray renderer for films, including The Last Starfighter.

Example program

[edit]

This is an example of a simple program that asks the user's name and exits, written in TRAC T64:[17]

#(DS,PROG.A,(
#(PS,(WHAT IS YOUR NAME?
))
#(DS,NAME,##(RS))
#(PS,(
GOODBYE))
))'

TRAC T84 uses a slightly different syntax and different names for its primitives. The following is a script to compute Fibonacci numbers, written in TRAC T84:[18]

:(s,fibo,(
:(ei,<1>, 1, 0,(
:(ei,<1>, 2, 1,(
:(aa, :(ri,fibo,:(as, <1>,1)),:(ri,fibo,:(as, <1>,2)))
))
))
))`
:(mw,fibo)'

See also

[edit]

References

[edit]
  1. ^ "TRAC T2001 Specification". February 5, 2005. Archived from the original on 2005-02-05.
  2. ^ "Trac 2001 programming language". SourceForge. March 8, 2013.
  3. ^ Jump up to: a b "TRAC – A man-machine string manipulating language". HOPL: Online Historical Encyclopaedia of Programming Languages. Archived from the original on August 13, 2009.
  4. ^ Jump up to: a b "Coding Supply — Everything a Programmer Needs". Archived from the original on 2001-04-08.
  5. ^ David Walden. "Macro Memories, 1964–2013". 2014.
  6. ^ Carol Loeb Mir. "A Comparison of String Handling in Four Programming Languages". 1972.
  7. ^ Jump up to: a b Mooers, C.N.; Deutsch, L.P. (1965). "TRAC, A Text-Handling Language". Proceeding ACM '65 Proceedings of the 1965 20th national conference. pp. 229–246. doi:10.1145/800197.806048. S2CID 40013081.
  8. ^ Kay, Alan (1969). The Reactive Engine (PhD). University of Utah.
  9. ^ Klaas van Schelven. "Don't say 'Homoiconic'".
  10. ^ McIlroy, M.D., Macro Instruction Extensions of Compiler Languages. CACM 3, No. 4 (1960), 214–220.
  11. ^ Eastwood, D.E. and McIlroy, M.D., Macro Compiler Modification of SAP. Bell Telephone Laboratories Computation Center, 1959.
  12. ^ McIlroy, M.D., Using SAP Macro Instructions to Manipulate Symbolic Expressions. Bell Telephone Laboratories Computation Center (1960)
  13. ^ Mooers, Calvin (22 June 1993). "Oral history interview with Calvin N. Mooers and Charlotte D. Mooers". Charles Babbage Institute. hdl:11299/107510.
  14. ^ "Dr. Dobb's Journal - Vol 1". 1976.
  15. ^ "DIESEL - Dumb Interpretively Evaluated String Expression Language". www.fourmilab.ch.
  16. ^ "Software Components / Embedded Systems". www.fourmilab.ch.
  17. ^ The Beginner's Manual for TRAC Language (1972) (archived) by Calvin N. Mooers.
  18. ^ TRAC information page (archived), at The History of Computing Project, with small code sample and photo of C. M. Mooers.
[edit]