TACPOL (programming language)
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. The article may be deleted if this message remains in place for seven days, i.e., after 00:11, 28 May 2024 (UTC). Find sources: "TACPOL" programming language – news · newspapers · books · scholar · JSTOR |
This article needs additional citations for verification. (July 2007) |
TACPOL (Tactical Procedure Oriented Language) is a block structured programming language developed by the United States Army for the TACFIRE Tactical Fire Direction command and control application. TACPOL is similar to PL/I.
Language constructs[edit]
Reserved words[edit]
Unlike PL/I, TACPOL keywords—called particles—are reserved words and cannot be used as identifiers. There are roughly 100 reserved words.
Identifiers[edit]
TACPOL identifiers can be any length, but if longer than eight characters only the first five concatenated with the last three characters were actually used.
Data types[edit]
TACPOL supports fixed-point binary numeric data, fixed-length character strings up to 512 bytes, and fixed-length bit strings up to 32 bits. There is no support for floating point numeric data or for pointers. Arrays may have up to three dimensions, but dynamic bounds are not permitted. Additional types are records, called groups, limited to a single level of nesting, tables (arrays of groups), and unions, called cells.
Control structures[edit]
Control structures include IF-THEN-ELSE, iteration, WHILE and CASE statements.
Procedures[edit]
Procedures may have value parameters, quantity parameters – by reference without type-checking, parameterless procedure and label parameters.
Implementations[edit]
The TACPOL compiler ran on and generated code for the AN/GYK-12, a militarized version of the Litton Industries L-3050 32-bit minicomputer.
Criticism and defense[edit]
Positive features[edit]
- TACPOL is easy to learn.[1]
Negative features[edit]
- "TACPOL has a large number of special language features which were included for reasons of efficiency because the inclusion of corresponding cleanly designed general purpose features was not properly understood."[2]
- "Cost per instruction of TACPOL [is] higher than language used for other military computers."[3]
Notes[edit]
References[edit]
- Litton Data Systems, Inc. (1975). TACPOL Reference Manual Programming Support System. Document USACSCS-TF-4-1.
External links[edit]
- TACPOL Reference Manual (USACSCS-TF-4-1)
- Serafino, et.al. "Report to the High Order Language Working Group" (1977)
- United States General Accounting Office. "Tactical Operations System Should Not Continue as Planned" (1979)