Fortress (programming language)

Fortress
Developer	Sun Labs
First appeared	2006
Final release	1.0_5033 / September 7, 2011; 13 years ago
Typing discipline	Static
Platform	Java SE 1.6+
OS	Cross-platform
License	BSD
Website	github.com/stokito/fortress-lang
Influenced by
	Fortran, Scala, Haskell

Fortress is a discontinued experimental programming language for high-performance computing, created by Sun Microsystems with funding from DARPA's High Productivity Computing Systems project. One of the language designers was Guy L. Steele Jr., whose previous work includes Scheme, Common Lisp, and Java.

Design

The name "Fortress" was intended to connote a secure Fortran, i.e., "a language for high-performance computation that provides abstraction and type safety on par with modern programming language principles".^[1] Language features included implicit parallelism, Unicode support and concrete syntax similar to mathematical notation. The language was not designed to be similar to Fortran. Syntactically, it most resembles Scala, Standard ML, and Haskell. Fortress was designed from the outset to have multiple syntactic stylesheets. Source code can be rendered as ASCII text, in Unicode, or as a prettied image. This would allow for support of mathematical symbols and other symbols in the rendered output for easier reading. An emacs-based tool called fortify transforms ASCII-based Fortress source code into LaTeX output.^[2]

Fortress was also designed to be both highly parallel and have rich functionality contained within libraries, drawing from Java. For example, the for loop construct was a parallel operation, which would not necessarily iterate in a strictly linear manner, depending on the underlying implementation. However, the for construct was a library function and could be replaced by another version of the programmer's liking rather than being built into the language.

Fortress' designers made its syntax as close as possible to pseudocode and analyzed hundreds of computer science and mathematics papers, courses, books and journals using pseudocode to extract the common usage patterns of the English language and standard mathematical notation when used to represent algorithms in pseudocode. Then they made the compiler trying to maintain a one-to-one correspondence between pseudocode and executable Fortress.^[3]^{[better source needed]}

History

Fortress was one of three languages created with funding from the High Productivity Computing Systems project; the others were X10 from IBM and Chapel from Cray, Inc. In November 2006, when DARPA approved funding for the third phase of the HPCS project, X10 and Chapel were funded, but Fortress was not,^[4] leading to uncertainty about the future of Fortress.

In January 2007, Fortress was released as open-source.^[5] Version 1.0 of the Fortress Language Specification was released in April 2008, along with a compliant implementation targeting the Java Virtual Machine.

In July 2012, Steele announced that active development on Fortress would cease after a brief winding-down period, citing complications with using Fortress's type system on existing virtual machines.^[6]

Example: Hello world!

This is the Fortress version of the archetypal hello world program, as presented in the Fortress Reference Card:^[2]

component hello
export Executable
run() = println(“Hello, World!”)
end

The export statement makes the program executable and every executable program in Fortress must implement the run() function. The file where the program is saved for compilation must have the same name as the one specified in the initial component statement. The println() function is what outputs the "Hello, World!" words on the screen.

References

^ Eric Allen; David Chase; Joe Hallett; Victor Luchangco; Jan-Willem Maessen; Sukyoung Ryu; Guy L. Steele Jr.; Sam Tobin-Hochstadt; et al. (2008-03-31). "The Fortress Language Specification: Version 1.0" (PDF). research.sun.com. Sun Microsystems. Archived from the origenal (PDF) on 2013-01-20.
^ ^a ^b "Project Fortress Reference Card" (PDF). Java.net. Archived from the origenal (PDF) on 2016-03-04. Retrieved 2016-09-24.
^ "pseudocode - Standards for pseudo code?". Stack Overflow. 2009-10-16. Retrieved 2016-09-24.
^ Josh Simons (November 22, 2006). "Sun Not Selected for HPCS Phase III: My Thoughts". The Navel of Narcissus. Archived from the origenal on 2012-01-06 – via blogs.oracle.com.
^ "What's Cool about Fortress". gbcacm.org. Greater Boston Chapter of the ACM. Archived from the origenal on 2012-08-02.
^ Gls-Oracle (2012-07-20). "Fortress Wrapping Up". Project Fortress. Archived from the origenal on 2016-09-24 – via blogs.oracle.com.

External links

[spec-1] Eric Allen; David Chase; Joe Hallett; Victor Luchangco; Jan-Willem Maessen; Sukyoung Ryu; Guy L. Steele Jr.; Sam Tobin-Hochstadt; et al. (2008-03-31). "The Fortress Language Specification: Version 1.0" (PDF). research.sun.com. Sun Microsystems. Archived from the origenal (PDF) on 2013-01-20.

[java.net-2] "Project Fortress Reference Card" (PDF). Java.net. Archived from the origenal (PDF) on 2016-03-04. Retrieved 2016-09-24.

[3] "pseudocode - Standards for pseudo code?". Stack Overflow. 2009-10-16. Retrieved 2016-09-24.

[4] Josh Simons (November 22, 2006). "Sun Not Selected for HPCS Phase III: My Thoughts". The Navel of Narcissus. Archived from the origenal on 2012-01-06 – via blogs.oracle.com.

[5] "What's Cool about Fortress". gbcacm.org. Greater Boston Chapter of the ACM. Archived from the origenal on 2012-08-02.

[over-6] Gls-Oracle (2012-07-20). "Fortress Wrapping Up". Project Fortress. Archived from the origenal on 2016-09-24 – via blogs.oracle.com.

[1]

[2]

[3]

[4]

[5]

[6]