#fortran — Public Fediverse posts

I have decided to call my work-in-progress FORTRAN-66 parser (and maybe eventually interpreter or compiler)... drumroll...

WHATFOR

Not to be confused with the University of Waterloo WATFOR, which presumably has seen little use after their release of WATFIV, which also presumably sees little use today.

#FORTRAN

I have decided to call my work-in-progress FORTRAN-66 parser (and maybe eventually interpreter or compiler)... drumroll...

WHATFOR

Not to be confused with the University of Waterloo WATFOR, which presumably has seen little use after their release of WATFIV, which also presumably sees little use today.

#FORTRAN

I have decided to call my work-in-progress FORTRAN-66 parser (and maybe eventually interpreter or compiler)... drumroll...

WHATFOR

Not to be confused with the University of Waterloo WATFOR, which presumably has seen little use after their release of WATFIV, which also presumably sees little use today.

#FORTRAN

I have decided to call my work-in-progress FORTRAN-66 parser (and maybe eventually interpreter or compiler)... drumroll...

WHATFOR

Not to be confused with the University of Waterloo WATFOR, which presumably has seen little use after their release of WATFIV, which also presumably sees little use today.

#FORTRAN

I have decided to call my work-in-progress FORTRAN-66 parser (and maybe eventually interpreter or compiler)... drumroll...

WHATFOR

Not to be confused with the University of Waterloo WATFOR, which presumably has seen little use after their release of WATFIV, which also presumably sees little use today.

#FORTRAN

The FORTRAN 66 syntax rules for arithmetic expressions are given in ASA X3.9-1966 §6.1.
These do not allow chained exponentiation without parenthesis, like:
A**B**C
but with parenthesis, either of the following are valid:
A**(B**C)
(A**B)**C
IBM FORTRAN IV allows the expression without parenthesis, and interprets chained exponentiation right-to-left, whereas the other arithmetic operators associate left-to-right.
I think many other FORTRAN compilers followed IBM's lead.
#FORTRAN
1/

The FORTRAN 66 syntax rules for arithmetic expressions are given in ASA X3.9-1966 §6.1.
These do not allow chained exponentiation without parenthesis, like:
A**B**C
but with parenthesis, either of the following are valid:
A**(B**C)
(A**B)**C
IBM FORTRAN IV allows the expression without parenthesis, and interprets chained exponentiation right-to-left, whereas the other arithmetic operators associate left-to-right.
I think many other FORTRAN compilers followed IBM's lead.
#FORTRAN
1/

The FORTRAN 66 syntax rules for arithmetic expressions are given in ASA X3.9-1966 §6.1.
These do not allow chained exponentiation without parenthesis, like:
A**B**C
but with parenthesis, either of the following are valid:
A**(B**C)
(A**B)**C
IBM FORTRAN IV allows the expression without parenthesis, and interprets chained exponentiation right-to-left, whereas the other arithmetic operators associate left-to-right.
I think many other FORTRAN compilers followed IBM's lead.
#FORTRAN
1/

The FORTRAN 66 syntax rules for arithmetic expressions are given in ASA X3.9-1966 §6.1.
These do not allow chained exponentiation without parenthesis, like:
A**B**C
but with parenthesis, either of the following are valid:
A**(B**C)
(A**B)**C
IBM FORTRAN IV allows the expression without parenthesis, and interprets chained exponentiation right-to-left, whereas the other arithmetic operators associate left-to-right.
I think many other FORTRAN compilers followed IBM's lead.
#FORTRAN
1/

The FORTRAN 66 syntax rules for arithmetic expressions are given in ASA X3.9-1966 §6.1.
These do not allow chained exponentiation without parenthesis, like:
A**B**C
but with parenthesis, either of the following are valid:
A**(B**C)
(A**B)**C
IBM FORTRAN IV allows the expression without parenthesis, and interprets chained exponentiation right-to-left, whereas the other arithmetic operators associate left-to-right.
I think many other FORTRAN compilers followed IBM's lead.
#FORTRAN
1/

First and foremost, Fortran is a vaat, comprehensive system. This,
alone, provides its own difficulties.
– IBM Systems Manual for 704 Fortran and 709 Fortran, April 1960
#FORTRAN

First and foremost, Fortran is a vaat, comprehensive system. This,
alone, provides its own difficulties.
– IBM Systems Manual for 704 Fortran and 709 Fortran, April 1960
#FORTRAN

First and foremost, Fortran is a vaat, comprehensive system. This,
alone, provides its own difficulties.
– IBM Systems Manual for 704 Fortran and 709 Fortran, April 1960
#FORTRAN

First and foremost, Fortran is a vaat, comprehensive system. This,
alone, provides its own difficulties.
– IBM Systems Manual for 704 Fortran and 709 Fortran, April 1960
#FORTRAN

First and foremost, Fortran is a vaat, comprehensive system. This,
alone, provides its own difficulties.
– IBM Systems Manual for 704 Fortran and 709 Fortran, April 1960
#FORTRAN

@scruss
I was just looking at an two DEC manuals for their 4K FORTRAN compiler for the PDP-8:
DIGITAL 8-2-S PDP-8 FORTRAN Programming Manual, 1964
DEC-08-AFCO PDP-8 4K FORTRAN Programmer's Reference Manual, 7ed.,arch 1970
#FORTRAN
1/

@scruss
I was just looking at an two DEC manuals for their 4K FORTRAN compiler for the PDP-8:
DIGITAL 8-2-S PDP-8 FORTRAN Programming Manual, 1964
DEC-08-AFCO PDP-8 4K FORTRAN Programmer's Reference Manual, 7ed.,arch 1970
#FORTRAN
1/

@scruss
I was just looking at an two DEC manuals for their 4K FORTRAN compiler for the PDP-8:
DIGITAL 8-2-S PDP-8 FORTRAN Programming Manual, 1964
DEC-08-AFCO PDP-8 4K FORTRAN Programmer's Reference Manual, 7ed.,arch 1970
#FORTRAN
1/

@scruss
I was just looking at an two DEC manuals for their 4K FORTRAN compiler for the PDP-8:
DIGITAL 8-2-S PDP-8 FORTRAN Programming Manual, 1964
DEC-08-AFCO PDP-8 4K FORTRAN Programmer's Reference Manual, 7ed.,arch 1970
#FORTRAN
1/

@scruss
I was just looking at an two DEC manuals for their 4K FORTRAN compiler for the PDP-8:
DIGITAL 8-2-S PDP-8 FORTRAN Programming Manual, 1964
DEC-08-AFCO PDP-8 4K FORTRAN Programmer's Reference Manual, 7ed.,arch 1970
#FORTRAN
1/

What makes some #programminglanguages last while others lose relevance? 🤔

Part 1 of this Andrew Oram series explores languages that appear immortal and those with respectable life cycles that receded. Discover the stories of C, C++, C#, #JavaScript, #Java, #PHP, #COBOL, #FORTRAN, #BASIC, #Rust, #Perl, and others 👇

https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

What makes some #programminglanguages last while others lose relevance? 🤔

Part 1 of this Andrew Oram series explores languages that appear immortal and those with respectable life cycles that receded. Discover the stories of C, C++, C#, #JavaScript, #Java, #PHP, #COBOL, #FORTRAN, #BASIC, #Rust, #Perl, and others 👇

https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

What makes some #programminglanguages last while others lose relevance? 🤔

Part 1 of this Andrew Oram series explores languages that appear immortal and those with respectable life cycles that receded. Discover the stories of C, C++, C#, #JavaScript, #Java, #PHP, #COBOL, #FORTRAN, #BASIC, #Rust, #Perl, and others 👇

https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

What makes some #programminglanguages last while others lose relevance? 🤔

Part 1 of this Andrew Oram series explores languages that appear immortal and those with respectable life cycles that receded. Discover the stories of C, C++, C#, #JavaScript, #Java, #PHP, #COBOL, #FORTRAN, #BASIC, #Rust, #Perl, and others 👇

https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

What makes some #programminglanguages last while others lose relevance? 🤔

Part 1 of this Andrew Oram series explores languages that appear immortal and those with respectable life cycles that receded. Discover the stories of C, C++, C#, #JavaScript, #Java, #PHP, #COBOL, #FORTRAN, #BASIC, #Rust, #Perl, and others 👇

https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

Если вы думаете, что знаете, чем отличается «Expression» от «Statement», то, скорее всего, вы ошибаетесь

Я занимаюсь изучением синтаксиса языков программирования и пытаюсь отделить фундаментальные закономерности от исторических случайностей. Одна из таких случайностей - почти повсеместное использование терминов выражение (expression) и инструкция (statement) при описании и классификации синтаксиса языков программирования. Интуитивно кажется, что 2 + 2 и if (x) { foo(); } - это совершенно разные сущности, но при более глубоком анализе оказывается, что подобное разделение искусственное и возникло из-за архитектурных особенностей вычислительных машин почти полвека назад и с тех пор просто «переходит» из языка в язык.

https://habr.com/ru/articles/1065722/

#lisp #rust #fortran #c++ #algol #expression #statement

Если вы думаете, что знаете, чем отличается «Expression» от «Statement», то, скорее всего, вы ошибаетесь

Я занимаюсь изучением синтаксиса языков программирования и пытаюсь отделить фундаментальные закономерности от исторических случайностей. Одна из таких случайностей - почти повсеместное использование терминов выражение (expression) и инструкция (statement) при описании и классификации синтаксиса языков программирования. Интуитивно кажется, что 2 + 2 и if (x) { foo(); } - это совершенно разные сущности, но при более глубоком анализе оказывается, что подобное разделение искусственное и возникло из-за архитектурных особенностей вычислительных машин почти полвека назад и с тех пор просто «переходит» из языка в язык.

https://habr.com/ru/articles/1065722/

#lisp #rust #fortran #c++ #algol #expression #statement

Если вы думаете, что знаете, чем отличается «Expression» от «Statement», то, скорее всего, вы ошибаетесь

Я занимаюсь изучением синтаксиса языков программирования и пытаюсь отделить фундаментальные закономерности от исторических случайностей. Одна из таких случайностей - почти повсеместное использование терминов выражение (expression) и инструкция (statement) при описании и классификации синтаксиса языков программирования. Интуитивно кажется, что 2 + 2 и if (x) { foo(); } - это совершенно разные сущности, но при более глубоком анализе оказывается, что подобное разделение искусственное и возникло из-за архитектурных особенностей вычислительных машин почти полвека назад и с тех пор просто «переходит» из языка в язык.

https://habr.com/ru/articles/1065722/

#lisp #rust #fortran #c++ #algol #expression #statement

What keeps some #programminglanguages relevant for decades while others fade away? 💻 🤔

In Part 1 of this Andrew Oram series, explore the different paths of C, C++, C#, #JavaScript, #Java, #Rust, #PHP, #COBOL, #FORTRAN, #BASIC, #Perl, and others 👇

https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

What keeps some #programminglanguages relevant for decades while others fade away? 💻 🤔

In Part 1 of this Andrew Oram series, explore the different paths of C, C++, C#, #JavaScript, #Java, #Rust, #PHP, #COBOL, #FORTRAN, #BASIC, #Perl, and others 👇

https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

What keeps some #programminglanguages relevant for decades while others fade away? 💻 🤔

In Part 1 of this Andrew Oram series, explore the different paths of C, C++, C#, #JavaScript, #Java, #Rust, #PHP, #COBOL, #FORTRAN, #BASIC, #Perl, and others 👇

https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

What keeps some #programminglanguages relevant for decades while others fade away? 💻 🤔

In Part 1 of this Andrew Oram series, explore the different paths of C, C++, C#, #JavaScript, #Java, #Rust, #PHP, #COBOL, #FORTRAN, #BASIC, #Perl, and others 👇

https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

What keeps some #programminglanguages relevant for decades while others fade away? 💻 🤔

In Part 1 of this Andrew Oram series, explore the different paths of C, C++, C#, #JavaScript, #Java, #Rust, #PHP, #COBOL, #FORTRAN, #BASIC, #Perl, and others 👇

https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

While perusing Jef Raskin’s documents from the early days of Apple (1979 predominately), I came across a curious one: a “calculator” language that Jef proposed.

What’s particularly interesting is that it’s presented in the context of programming languages. Its specification doesn’t really describe a general purpose programming language – the title is accurate in that it is a calculator […]

While perusing Jef Raskin’s documents from the early days of Apple (1979 predominately), I came across a curious one: a “calculator” language that Jef proposed.

What’s particularly interesting is that it’s presented in the context of programming languages. Its specification doesn’t really describe a general purpose programming language – the title is accurate in that it is a calculator […]

While perusing Jef Raskin’s documents from the early days of Apple (1979 predominately), I came across a curious one: a “calculator” language that Jef proposed.

What’s particularly interesting is that it’s presented in the context of programming languages. Its specification doesn’t really describe a general purpose programming language – the title is accurate in that it is a calculator […]

While perusing Jef Raskin’s documents from the early days of Apple (1979 predominately), I came across a curious one: a “calculator” language that Jef proposed.

What’s particularly interesting is that it’s presented in the context of programming languages. Its specification doesn’t really describe a general purpose programming language – the title is accurate in that it is a calculator […]

This is already a week old (busy, busy, busy) but a #JOSS paper I reviewed has been published: Fortitude, the #Fortran Linter

https://joss.theoj.org/papers/10.21105/joss.10570

This is one of the coolest projects in the Fortran world today, and catches a huge variety of common problems through static analysis built on roff. Congratulations to the authors on the publication 🎉🎉 and if you're a Fortran developer go install and use it now!

This is already a week old (busy, busy, busy) but a #JOSS paper I reviewed has been published: Fortitude, the #Fortran Linter

https://joss.theoj.org/papers/10.21105/joss.10570

This is one of the coolest projects in the Fortran world today, and catches a huge variety of common problems through static analysis built on roff. Congratulations to the authors on the publication 🎉🎉 and if you're a Fortran developer go install and use it now!

This is already a week old (busy, busy, busy) but a #JOSS paper I reviewed has been published: Fortitude, the #Fortran Linter

https://joss.theoj.org/papers/10.21105/joss.10570

This is one of the coolest projects in the Fortran world today, and catches a huge variety of common problems through static analysis built on roff. Congratulations to the authors on the publication 🎉🎉 and if you're a Fortran developer go install and use it now!

This is already a week old (busy, busy, busy) but a #JOSS paper I reviewed has been published: Fortitude, the #Fortran Linter

https://joss.theoj.org/papers/10.21105/joss.10570

This is one of the coolest projects in the Fortran world today, and catches a huge variety of common problems through static analysis built on roff. Congratulations to the authors on the publication 🎉🎉 and if you're a Fortran developer go install and use it now!

Does anyone have the NBS Special Publication 399 (SP399) NBS FORTRAN Test Programs for Fortran-66 in machine-readable form? Scans of the printed listings are online, though as typical with scans, there are some errors introduced, e.g., truncated lines on Volume 2 page 10.
The tape is no longer available from NIST, but was, AFAICT, freely redistributable.
1/
#FORTRAN

Does anyone have the NBS Special Publication 399 (SP399) NBS FORTRAN Test Programs for Fortran-66 in machine-readable form? Scans of the printed listings are online, though as typical with scans, there are some errors introduced, e.g., truncated lines on Volume 2 page 10.
The tape is no longer available from NIST, but was, AFAICT, freely redistributable.
1/
#FORTRAN

Does anyone have the NBS Special Publication 399 (SP399) NBS FORTRAN Test Programs for Fortran-66 in machine-readable form? Scans of the printed listings are online, though as typical with scans, there are some errors introduced, e.g., truncated lines on Volume 2 page 10.
The tape is no longer available from NIST, but was, AFAICT, freely redistributable.
1/
#FORTRAN

Does anyone have the NBS Special Publication 399 (SP399) NBS FORTRAN Test Programs for Fortran-66 in machine-readable form? Scans of the printed listings are online, though as typical with scans, there are some errors introduced, e.g., truncated lines on Volume 2 page 10.
The tape is no longer available from NIST, but was, AFAICT, freely redistributable.
1/
#FORTRAN

Does anyone have the NBS Special Publication 399 (SP399) NBS FORTRAN Test Programs for Fortran-66 in machine-readable form? Scans of the printed listings are online, though as typical with scans, there are some errors introduced, e.g., truncated lines on Volume 2 page 10.
The tape is no longer available from NIST, but was, AFAICT, freely redistributable.
1/
#FORTRAN

Some #programminglanguages remain widely used for decades, while others fulfill an important role during their time before receding.

Our author Andrew Oram explores the stories of C, C++, C#, #Java, #JavaScript, #PHP, #Rust, #Perl, #COBOL, #FORTRAN, #BASIC and others. Dive into it 👇
https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

Some #programminglanguages remain widely used for decades, while others fulfill an important role during their time before receding.

Our author Andrew Oram explores the stories of C, C++, C#, #Java, #JavaScript, #PHP, #Rust, #Perl, #COBOL, #FORTRAN, #BASIC and others. Dive into it 👇
https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

Some #programminglanguages remain widely used for decades, while others fulfill an important role during their time before receding.

Our author Andrew Oram explores the stories of C, C++, C#, #Java, #JavaScript, #PHP, #Rust, #Perl, #COBOL, #FORTRAN, #BASIC and others. Dive into it 👇
https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

Some #programminglanguages remain widely used for decades, while others fulfill an important role during their time before receding.

Our author Andrew Oram explores the stories of C, C++, C#, #Java, #JavaScript, #PHP, #Rust, #Perl, #COBOL, #FORTRAN, #BASIC and others. Dive into it 👇
https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

Some #programminglanguages remain widely used for decades, while others fulfill an important role during their time before receding.

Our author Andrew Oram explores the stories of C, C++, C#, #Java, #JavaScript, #PHP, #Rust, #Perl, #COBOL, #FORTRAN, #BASIC and others. Dive into it 👇
https://lpi.org/xq3f

#LPI #programming #opensource #linux #unix #softwaredevelopment #coding #developers #sysadmins #python #softwareengineering

I'm still annoyed that Microsoft FORTRAN-80 is an implementation of FORTRAN IV and FORTRAN-66, and not of FORTRAN-77.
Late versions of Microsoft FORTRAN-80 did have the IMPLICIT NONE, which wasn't standardized until MIL-STD-1753, which extended FORTRAN-77.
#fortran #fortraniv #fortran66 #fortran77 #microsoft #fortran80
[EDITED: correction re IMPLICIT NONE thanks to @arclight ]

I'm still annoyed that Microsoft FORTRAN-80 is an implementation of FORTRAN IV and FORTRAN-66, and not of FORTRAN-77.
Late versions of Microsoft FORTRAN-80 did have the IMPLICIT NONE, which wasn't standardized until MIL-STD-1753, which extended FORTRAN-77.
#fortran #fortraniv #fortran66 #fortran77 #microsoft #fortran80
[EDITED: correction re IMPLICIT NONE thanks to @arclight ]

I'm still annoyed that Microsoft FORTRAN-80 is an implementation of FORTRAN IV and FORTRAN-66, and not of FORTRAN-77.
Late versions of Microsoft FORTRAN-80 did have the IMPLICIT NONE, which wasn't standardized until MIL-STD-1753, which extended FORTRAN-77.
#fortran #fortraniv #fortran66 #fortran77 #microsoft #fortran80
[EDITED: correction re IMPLICIT NONE thanks to @arclight ]

I'm still annoyed that Microsoft FORTRAN-80 is an implementation of FORTRAN IV and FORTRAN-66, and not of FORTRAN-77.
Late versions of Microsoft FORTRAN-80 did have the IMPLICIT NONE, which wasn't standardized until MIL-STD-1753, which extended FORTRAN-77.
#fortran #fortraniv #fortran66 #fortran77 #microsoft #fortran80
[EDITED: correction re IMPLICIT NONE thanks to @arclight ]

I'm still annoyed that Microsoft FORTRAN-80 is an implementation of FORTRAN IV and FORTRAN-66, and not of FORTRAN-77.
Late versions of Microsoft FORTRAN-80 did have the IMPLICIT NONE, which wasn't standardized until MIL-STD-1753, which extended FORTRAN-77.
#fortran #fortraniv #fortran66 #fortran77 #microsoft #fortran80
[EDITED: correction re IMPLICIT NONE thanks to @arclight ]

[In 1959]
"FORTRAN was provided for the IBM 1401 computer by an innovative 63-phase compiler that ran entirely in its core memory of only 8000 (six-bit) characters. The compiler could be run from tape, or from a 2200-card deck; it used no further tape or disk storage. "

https://en.wikipedia.org/wiki/Fortran
#fortran

[In 1959]
"FORTRAN was provided for the IBM 1401 computer by an innovative 63-phase compiler that ran entirely in its core memory of only 8000 (six-bit) characters. The compiler could be run from tape, or from a 2200-card deck; it used no further tape or disk storage. "

https://en.wikipedia.org/wiki/Fortran
#fortran

[In 1959]
"FORTRAN was provided for the IBM 1401 computer by an innovative 63-phase compiler that ran entirely in its core memory of only 8000 (six-bit) characters. The compiler could be run from tape, or from a 2200-card deck; it used no further tape or disk storage. "

https://en.wikipedia.org/wiki/Fortran
#fortran

[In 1959]
"FORTRAN was provided for the IBM 1401 computer by an innovative 63-phase compiler that ran entirely in its core memory of only 8000 (six-bit) characters. The compiler could be run from tape, or from a 2200-card deck; it used no further tape or disk storage. "

https://en.wikipedia.org/wiki/Fortran
#fortran