Skip to content
0
  • Home
  • Piero Bosio
  • Blog
  • World
  • Fediverso
  • News
  • Categories
  • Old Web Site
  • Recent
  • Popular
  • Tags
  • Users
  • Home
  • Piero Bosio
  • Blog
  • World
  • Fediverso
  • News
  • Categories
  • Old Web Site
  • Recent
  • Popular
  • Tags
  • Users
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone
mcc@mastodon.socialundefined

mcc

@mcc@mastodon.social
About
Posts
1.1k
Topics
379
Shares
0
Groups
0
Followers
0
Following
0

View Original

Posts

Recent Best Controversial

  • ME: I do not need "AI code assistants" because I have a keyboard with a functioning "control" key.
    mcc@mastodon.socialundefined mcc@mastodon.social

    ME: I do not need "AI code assistants" because I have a keyboard with a functioning "control" key.

    THE "CONTROL" KEY ON MY KEYBOARD: *breaks*

    ME: *sweats profusely*

    Uncategorized

  • So for a long time I found LISP elegant but I found the syntax infuriating.
    mcc@mastodon.socialundefined mcc@mastodon.social

    Wait. Can you write GUIX flakes (or whatever they're called) in Wisp?

    https://merveilles.town/@aartaka/116054295778478105

    Uncategorized

  • So for a long time I found LISP elegant but I found the syntax infuriating.
    mcc@mastodon.socialundefined mcc@mastodon.social

    @aartaka I think it's very interesting!

    I didn't know it was an option for Guix. That's good to know.

    Uncategorized

  • So for a long time I found LISP elegant but I found the syntax infuriating.
    mcc@mastodon.socialundefined mcc@mastodon.social

    @akkartik Oh, multibranch if makes sense.

    I'm actually doing a vaguely bizarre thing where the if statement can have an optional "else" because "else" is a global symbol which is defined as "false". If the symbol is non-false (eg, a block) it's treated as a case. i'm considering defining "elif" as "true" and special-casing that to determine whether the next item is a case or a condition.

    Uncategorized

  • So for a long time I found LISP elegant but I found the syntax infuriating.
    mcc@mastodon.socialundefined mcc@mastodon.social

    @akkartik By the way, something that may not be obvious in my sample code. I said {} is "lambda", but I was simplifying for space. {} is an argument-less lambda. In fact, {a b, c d} is shorthand for '((a b)(c d)). You upgrade a quoted list (a {}) to a function by passing it to the fn or set-fn builtin functions.

    Uncategorized

  • So for a long time I found LISP elegant but I found the syntax infuriating.
    mcc@mastodon.socialundefined mcc@mastodon.social

    @akkartik Are there any examples of cond in the examples list above?

    Uncategorized

  • So for a long time I found LISP elegant but I found the syntax infuriating.
    mcc@mastodon.socialundefined mcc@mastodon.social

    @akkartik This was my approach to cond, I called it the "match" statement

    https://codeberg.org/mcc/nameless-experimental-lisp/src/branch/unstable/sample/aoc/2024-day6-part1.l0#L167

    I think it's quite readable, but when writing it it's a bit frictiony to have to remember when to use [], when to use {}, and when to use () to get the results you wanted. (Note "match" is a *function* defined further up in the file; this LISP has no special forms, even the {}:. syntax isn't special forms, it's just inserting (, ) and ' in various ways.)

    Uncategorized

  • So for a long time I found LISP elegant but I found the syntax infuriating.
    mcc@mastodon.socialundefined mcc@mastodon.social

    @akkartik Since this means that most lone words alone on a line are noops, to be "helpful", the interpreter treats it as an error when it encounters a lone-word statement (unless that statement is the final line of a {} block, in which case it is returned as the evaluation result of the block)

    Uncategorized

  • So for a long time I found LISP elegant but I found the syntax infuriating.
    mcc@mastodon.socialundefined mcc@mastodon.social

    @akkartik ( is inserted at start of line, ) is inserted at end of line. An unclosed ({[ within a line extends the line. A blank line is ignored. so yeah, one ( before the "print", one ) after the "sp".

    Single word on a line is the grammar's one awkward case. Single word on a line is *exempt* from the () wrapping. This is because otherwise the [] list blocks would be very hard to form sensibly. A bare word on a line is treated as just that word's value, and it's not executed like a function.

    Uncategorized

  • So for a long time I found LISP elegant but I found the syntax infuriating.
    mcc@mastodon.socialundefined mcc@mastodon.social

    @lobo oh gosh i'm so glad you noticed this because this was LITERALLY my attempt to make a LISP that felt like TCL. I learned TCL and was like "this is compelling but too unhygenic, what if I made something halfway between TCL and LISP"

    Uncategorized

  • So for a long time I found LISP elegant but I found the syntax infuriating.
    mcc@mastodon.socialundefined mcc@mastodon.social

    ( Look how fundamentally un-LISP-y my LISP is. I'm proud of it. https://codeberg.org/mcc/nameless-experimental-lisp/src/branch/unstable/sample/fizzbuzz.l0 )

    EDIT: Wait, I think this sample code might be a bit out of date… this is from before the language had a "while" builtin, so it defines a "while" operation in terms of "if".

    Uncategorized

  • So for a long time I found LISP elegant but I found the syntax infuriating.
    mcc@mastodon.socialundefined mcc@mastodon.social

    So for a long time I found LISP elegant but I found the syntax infuriating. Then I made my own LISP variant with semi-significant whitespace and helper syntax— each line (up to whitespace or comma) is wrapped in an implicit (), a : wraps a () to the end of the line, a {} wraps its interior in (lambda), a [] wraps its contents in (list ), "x.y" becomes "get x y". Suddenly, I found it usable!

    I wonder if I could just make an editor that applies these rules implicitly, and then I could use GUIX.

    Uncategorized

  • Wowwww Mastodon custom emoji misgendering me 🤷‍♀️
    mcc@mastodon.socialundefined mcc@mastodon.social

    @noiob Shrugging is gendered?? :O

    Uncategorized

  • Wowwww Mastodon custom emoji misgendering me 🤷‍♀️
    mcc@mastodon.socialundefined mcc@mastodon.social

    @jplebreton https://beige.party/@mayintoronto/116049687815641210

    Uncategorized

  • Wowwww Mastodon custom emoji misgendering me 🤷‍♀️
    mcc@mastodon.socialundefined mcc@mastodon.social

    @mayintoronto *looking down* ok so this shirt is green but i actually have one that's exactly the same but purple brb

    Uncategorized

  • Wowwww Mastodon custom emoji misgendering me 🤷‍♀️
    mcc@mastodon.socialundefined mcc@mastodon.social

    @mayintoronto "you can tell i'm a woman because i'm wearing a purple shirt"

    Uncategorized

  • Wowwww Mastodon custom emoji misgendering me 🤷‍♀️
    mcc@mastodon.socialundefined mcc@mastodon.social

    (The actual problem was that I accidentally used the generic "shrugging person" emoji instead of the explicit "shrugging woman" emoji, and Windows 10 made a different decision from the Mastodon emoji set about default genders¹. Meaning there's not actually a problem except that emoji are somehow a form of ideogram which is subjective depending on who is viewing it.)

    ¹ https://magicalpessimism.bandcamp.com/track/when-its-over-ft-no-rome

    Uncategorized

  • Wowwww Mastodon custom emoji misgendering me 🤷‍♀️
    mcc@mastodon.socialundefined mcc@mastodon.social

    Wowwww Mastodon custom emoji misgendering me 🤷‍♀️

    Uncategorized

  • CHALLENGE: Do picture-in-picture for a YouTube window without crashing Wayland
    mcc@mastodon.socialundefined mcc@mastodon.social

    CHALLENGE: Do picture-in-picture for a YouTube window without crashing Wayland

    THE CONTESTANTS: Debian 13, Firefox 140.6.0esr

    OUTCOME: Abject failure

    Uncategorized

  • This post did not contain any content.
    mcc@mastodon.socialundefined mcc@mastodon.social

    @bob Personally I do not

    Uncategorized
  • 1
  • 2
  • 3
  • 4
  • 5
  • 56
  • 57
  • 1 / 57
  • Login

  • Login or register to search.
  • First post
    Last post