• 0 posts
  • 4 comments
Joined 2 years ago
Cake day: June 25th, 2024
  • Your daily weather forecast likely runs on FORTRAN. It’s quite terrible code in many places because the people writing it are not software engineers but meteorologists, mathematicians, or physicists with little to no formal training in software design writing a million-line behemoth.

    And FORTRAN adds to the suck because it is superbly verbose, lacks generics, has a few really bad language design decisions carried over from the 60’s, and a thoroughly half-assed object model tacked on. As a cherry on top, the compilers are terrible because nobody uses the language anymore – especially the more recent features (2003 and later).

  • I’ve been a four-star programmer a few times. Imagine a blocked symmetric matrix where the rows and columns are indexed by triples (u,v,w). The entries are zero whenever u != u’ or v != v’, and because of symmetry you only store entries with w <= w’. But the range of v depends on the value of u and the range of w on the value of v. So you do

    double ****mat = calloc (UMAX, sizeof(*mat));
    for (int u = 0; u < UMAX; ++u) {
      mat[u] = calloc (u + 1, sizeof(**mat));
      for (int v = 0; v <= u; ++v) {
        mat[u][v] = calloc (v + 1, sizeof(***mat));
        for (int w = 0; w <= v; ++w) {
          mat[u][v][w] = calloc (w + 1, sizeof(****mat));
          for (int ww = 0; ww <= w; ++ww)
            mat[u][v][w][ww] = some_function (u, v, w, ww);
        }
      }
    }
    

    and weep a little. In reality, this gets a bit optimized by allocating a single chunk of memory and carving that up into the pointer and data arrays, so everything is reasonably close together in memory.