home.social

#proceduralprogramming — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #proceduralprogramming, aggregated by home.social.

  1. @kentpitman

    Thank you!
    Indeed your post is a good read and instructive on many counts.

    Three notes:

    (1)
    «=====
    (LOOP FOR X FROM 3 TO 5 COLLECT X)
    (3 4 5)

    (LOOP COLLECT X FOR X FROM 3 TO 5)
    (3 4 5 6)
    =====»

    This is an important example (and a good catch), which has "procedural" written all over it and it shows that `loop' isn't actually declarative—it can only be viewed as such, carefully.

    It seems to me that it would be interesting to fix the second case, rather than prohibit it, _but_ it may be difficult to justify the effort.
    (Regrettably, I can't recall exactly what the _current_ Common Lisp specification says, but I'll check later.)

    (2)
    Yes, I have always found the design and history of the pathname system very instructive, in more ways than I can elaborate now.
    And let no one forget about logical pathnames, too.

    "LOSSAG" fit in a single 36-bit word, didn't it?

    As a footnote, a long time ago I was something of a user of old IBM mainframe operating systems like VM/370¹, which did not have directories and separated a file name from a file type with a space (each up to eight characters, no lower case).
    _________
    ¹ Bulgaria was lagging behind the technological times then.

    (3)
    It's interesting to mention an emulator in this context.
    I can see a weak analogy to historical reconstructions.
    (There are many people who do them, mostly as recreation.
    I have been to some, watching horse riders shoot arrows and sheltering in a 7th-century-model tent from the rain.)

    #CommonLisp
    #ComputerHistory
    #DeclarativeProgramming
    #DeclarativeStyle
    #History
    #Lisp
    #ProceduralProgramming
    #ProceduralStyle

    @screwlisp

  2. Just completed day 4 of this year's Advent of Code:
    gist.github.com/and-kal/da2371

    Actually a pretty good way to get familiar with a new programming language.
    Though that's probably some super inefficient #Lua code and loopy as hell. But I think there's something nice about its #naïveté.

    adventofcode.com/2024

    #AdventOfCode #AdventOfCode2024 #proceduralprogramming #ifthen

  3. Just completed day 4 of this year's Advent of Code:
    gist.github.com/and-kal/da2371

    Actually a pretty good way to get familiar with a new programming language.
    Though that's probably some super inefficient #Lua code and loopy as hell. But I think there's something nice about its #naïveté.

    adventofcode.com/2024

    #AdventOfCode #AdventOfCode2024 #proceduralprogramming #ifthen

  4. Just completed day 4 of this year's Advent of Code:
    gist.github.com/and-kal/da2371

    Actually a pretty good way to get familiar with a new programming language.
    Though that's probably some super inefficient #Lua code and loopy as hell. But I think there's something nice about its #naïveté.

    adventofcode.com/2024

    #AdventOfCode #AdventOfCode2024 #proceduralprogramming #ifthen

  5. Just completed day 4 of this year's Advent of Code:
    gist.github.com/and-kal/da2371

    Actually a pretty good way to get familiar with a new programming language.
    Though that's probably some super inefficient #Lua code and loopy as hell. But I think there's something nice about its #naïveté.

    adventofcode.com/2024

    #AdventOfCode #AdventOfCode2024 #proceduralprogramming #ifthen