Quote from the FORTRAN manual for Xerox computers:

"The primary purpose of the DATA statement is to give names to constants; instead of referring to pi as 3.141592653589793 at every appearance, the variable PI can be given that value with a DATA statement and used instead of the longer form of the constant. This also simplifies modifying the program, should the value of pi change."

Non-Euclidean Doom: what happens to a game when pi is not 3.14159…

media.ccc.de
@shelldozer Ironically, the value of PI is much more likely to change if your code doesn't use named constants. A hallmark of most scientific software is the inconsistent precision applied to well-known physical and numerical constants. You're likely to find literal values of ln(2), g, and π written in at least 3 different precisions through a code.
@shelldozer Want to drive lazy scientists and engineers nuts? Require citation to the canonical source of every physical constant used in a code.
"What?! Everyone knows g is 9.8 m/s2"
"Then it should be trivial to provide a reference (points at most recent CODATA release on NIST website)"
"(Angry typing) FINE. Happy now?"
"Nice. Now do Boltzmann's constant and every other constant whose value you just pulled out of your ass in this code..."
@arclight Although, pedantically, such cases are really just *different* *constants*.

@shelldozer @arclight

"One man's constant is another man's variable." Alan Perlis.

Osborn's Law: Constants aren't, variables don't.

(with apologies for the implicit sexism that was the norm in 1982)

@shelldozer

Let's change the value of pi!!

@kingu @shelldozer
It's been tried :-)
(Indiana Pi bill 1897)
Indiana Almost Made Pi Equal to 3.2, and Other Pi Day Facts

As you celebrate the mathematical holiday, here's a history of notable moments in the irrational number's past

Smithsonian Magazine
@shelldozer In certain old IBM FORTRAN versions, it's possible to redefine constants. Redefining 1 to be equivalent to the value of 2 can be quite hilarious