home.social

#versu — Public Fediverse posts

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

  1. The expansions generating that code look something like this. #suetum #versu #praxis

  2. The expansions generating that code look something like this. #suetum #versu #praxis

  3. The expansions generating that code look something like this. #suetum #versu #praxis

  4. Well, even though I was working on Selanía too these days, I've been able to get to the end of the expansion mechanism too! Now I can write stuff like

    ```
    Have you heard of what [Gossippee.subj] said yesterday?
    No! What did [Gossippee.subj] do?
    Well, you know, someone gave [Gossippee.obj] the excuse to...
    ```

    And have it expand to

    ```
    Have you heard of what Mary said yesterday?
    No! What did she do?
    Well, you know, someone gave her the excuse to...
    ```

    #suetum #versu #praxis

  5. Well, even though I was working on Selanía too these days, I've been able to get to the end of the expansion mechanism too! Now I can write stuff like

    ```
    Have you heard of what [Gossippee.subj] said yesterday?
    No! What did [Gossippee.subj] do?
    Well, you know, someone gave [Gossippee.obj] the excuse to...
    ```

    And have it expand to

    ```
    Have you heard of what Mary said yesterday?
    No! What did she do?
    Well, you know, someone gave her the excuse to...
    ```

    #suetum #versu #praxis

  6. Well, even though I was working on Selanía too these days, I've been able to get to the end of the expansion mechanism too! Now I can write stuff like

    ```
    Have you heard of what [Gossippee.subj] said yesterday?
    No! What did [Gossippee.subj] do?
    Well, you know, someone gave [Gossippee.obj] the excuse to...
    ```

    And have it expand to

    ```
    Have you heard of what Mary said yesterday?
    No! What did she do?
    Well, you know, someone gave her the excuse to...
    ```

    #suetum #versu #praxis

  7. In order to expand strings like
    "Hello, [greeting.towards.Person]."
    I must know context about Person (like: do I hate them? I love them? I'm neutral?), which means that intelligent expansions must be used (context free grammars with conditions from the current state of the game, in practice), which means that they are not just syntactic replacement but need the whole machinery of the runtime engine, which means moving lots of code... AAAAA xD

    #Suetum #versu #praxis

  8. In order to expand strings like
    "Hello, [greeting.towards.Person]."
    I must know context about Person (like: do I hate them? I love them? I'm neutral?), which means that intelligent expansions must be used (context free grammars with conditions from the current state of the game, in practice), which means that they are not just syntactic replacement but need the whole machinery of the runtime engine, which means moving lots of code... AAAAA xD

    #Suetum #versu #praxis

  9. In order to expand strings like
    "Hello, [greeting.towards.Person]."
    I must know context about Person (like: do I hate them? I love them? I'm neutral?), which means that intelligent expansions must be used (context free grammars with conditions from the current state of the game, in practice), which means that they are not just syntactic replacement but need the whole machinery of the runtime engine, which means moving lots of code... AAAAA xD

    #Suetum #versu #praxis

  10. Parsing code + test suite done, so now I can go on with the compilation and then execution of the expansion! #suetum #versu #praxis

  11. Parsing code + test suite done, so now I can go on with the compilation and then execution of the expansion! #suetum #versu #praxis

  12. Parsing code + test suite done, so now I can go on with the compilation and then execution of the expansion! #suetum #versu #praxis

  13. ok, after some bugfix I reached the astronomical amount of...
    (drumrolls)
    48 lines of antlr4 parser.
    i love so much when i can code less O_O
    #suetum #praxis #versu

  14. ok, after some bugfix I reached the astronomical amount of...
    (drumrolls)
    48 lines of antlr4 parser.
    i love so much when i can code less O_O
    #suetum #praxis #versu

  15. ok, after some bugfix I reached the astronomical amount of...
    (drumrolls)
    48 lines of antlr4 parser.
    i love so much when i can code less O_O
    #suetum #praxis #versu

  16. Lots of thinking, and then the grammar for the expansion construct is so embarrassingly simple 🥹 #Suetum #versu #praxis

  17. Lots of thinking, and then the grammar for the expansion construct is so embarrassingly simple 🥹 #Suetum #versu #praxis

  18. Lots of thinking, and then the grammar for the expansion construct is so embarrassingly simple 🥹 #Suetum #versu #praxis

  19. Fixed also the last bug regarding axiom/rules exploration. Which allows you to drill-down in axiom expansions, and sub-axiom expansions and so on.

    Now, in the space between the work on Selanìa, I can get to attack (my version of) Prolog's definite clause grammars.

    It will probably be a more pragmatic approach, strongly oriented towards the narrative usages, with dedicated syntax, although it will be 100% based on exclusion logic like the rest.

    #Suetum #versu #praxis

  20. Fixed also the last bug regarding axiom/rules exploration. Which allows you to drill-down in axiom expansions, and sub-axiom expansions and so on.

    Now, in the space between the work on Selanìa, I can get to attack (my version of) Prolog's definite clause grammars.

    It will probably be a more pragmatic approach, strongly oriented towards the narrative usages, with dedicated syntax, although it will be 100% based on exclusion logic like the rest.

    #Suetum #versu #praxis

  21. Fixed also the last bug regarding axiom/rules exploration. Which allows you to drill-down in axiom expansions, and sub-axiom expansions and so on.

    Now, in the space between the work on Selanìa, I can get to attack (my version of) Prolog's definite clause grammars.

    It will probably be a more pragmatic approach, strongly oriented towards the narrative usages, with dedicated syntax, although it will be 100% based on exclusion logic like the rest.

    #Suetum #versu #praxis

  22. Big commit on #Suetum to improve axioms (rules). Now you can write mutually recursive rules, and Habitus is also kind-of able to show them (there are still cases in which it can't expand an axiom, in case the very first rule of the axiom already fails)!

    codeberg.org/owofgames/suetum/

    #praxis #versu

  23. Big commit on #Suetum to improve axioms (rules). Now you can write mutually recursive rules, and Habitus is also kind-of able to show them (there are still cases in which it can't expand an axiom, in case the very first rule of the axiom already fails)!

    codeberg.org/owofgames/suetum/

    #praxis #versu

  24. Big commit on #Suetum to improve axioms (rules). Now you can write mutually recursive rules, and Habitus is also kind-of able to show them (there are still cases in which it can't expand an axiom, in case the very first rule of the axiom already fails)!

    codeberg.org/owofgames/suetum/

    #praxis #versu

  25. This #Suetum program is doing like a thousand more computations than it should to check a condition, but at least the indented logger produces a very pleasing minimap on the right of the editor.

    #versu #praxis

  26. This #Suetum program is doing like a thousand more computations than it should to check a condition, but at least the indented logger produces a very pleasing minimap on the right of the editor.

    #versu #praxis

  27. This #Suetum program is doing like a thousand more computations than it should to check a condition, but at least the indented logger produces a very pleasing minimap on the right of the editor.

    #versu #praxis

  28. I kind of, sort of forgot that axioms are parts of the system, and right now they are completely opaque to the debugger.

    So! Let's expand the system the allows for notifications during the unification of logic clauses to work also on axioms, and track a "stack" of the resolution.

    This was quite tricky, and revealed a bug in recursive axiom applications, but: it's done! Now, how to properly display it...

    #Suetum #versu #praxis

  29. I kind of, sort of forgot that axioms are parts of the system, and right now they are completely opaque to the debugger.

    So! Let's expand the system the allows for notifications during the unification of logic clauses to work also on axioms, and track a "stack" of the resolution.

    This was quite tricky, and revealed a bug in recursive axiom applications, but: it's done! Now, how to properly display it...

    #Suetum #versu #praxis

  30. I kind of, sort of forgot that axioms are parts of the system, and right now they are completely opaque to the debugger.

    So! Let's expand the system the allows for notifications during the unification of logic clauses to work also on axioms, and track a "stack" of the resolution.

    This was quite tricky, and revealed a bug in recursive axiom applications, but: it's done! Now, how to properly display it...

    #Suetum #versu #praxis

  31. The work on the debugging tool for #Suetum is reaching its completion, but this is the most dense part, conceptually.

    Added the possibility to see the agents' heuristics, to time travel (!) between the current and past states of the simulations, and what I'm now working on is the ability of creating "alternative" world states, where you simulate a different choice from the one picked by the game purely inside the debugging tool.

    #praxis #versu

  32. The work on the debugging tool for #Suetum is reaching its completion, but this is the most dense part, conceptually.

    Added the possibility to see the agents' heuristics, to time travel (!) between the current and past states of the simulations, and what I'm now working on is the ability of creating "alternative" world states, where you simulate a different choice from the one picked by the game purely inside the debugging tool.

    #praxis #versu

  33. The work on the debugging tool for #Suetum is reaching its completion, but this is the most dense part, conceptually.

    Added the possibility to see the agents' heuristics, to time travel (!) between the current and past states of the simulations, and what I'm now working on is the ability of creating "alternative" world states, where you simulate a different choice from the one picked by the game purely inside the debugging tool.

    #praxis #versu

  34. So, apparently, yes: it was a matter of an afternoon to add support for forall/exists quantification in #Suetum 😮

    (also added the possibility to explore the bindings that matched the conditions, to debug problems in matching, and set an icon too)

    #praxis #versu

  35. So, apparently, yes: it was a matter of an afternoon to add support for forall/exists quantification in #Suetum 😮

    (also added the possibility to explore the bindings that matched the conditions, to debug problems in matching, and set an icon too)

    #praxis #versu

  36. So, apparently, yes: it was a matter of an afternoon to add support for forall/exists quantification in #Suetum 😮

    (also added the possibility to explore the bindings that matched the conditions, to debug problems in matching, and set an icon too)

    #praxis #versu

  37. Welp, looks like "for all" and "exists" operator are indeed necessary to build logic programs like i need.

    So, this afternoon will be dedicated to that... because it will be... very... simple... to add quantifiers... right? >_>

    #suetum #versu #praxis

  38. Welp, looks like "for all" and "exists" operator are indeed necessary to build logic programs like i need.

    So, this afternoon will be dedicated to that... because it will be... very... simple... to add quantifiers... right? >_>

    #suetum #versu #praxis

  39. Welp, looks like "for all" and "exists" operator are indeed necessary to build logic programs like i need.

    So, this afternoon will be dedicated to that... because it will be... very... simple... to add quantifiers... right? >_>

    #suetum #versu #praxis

  40. *cone of shame, pt. 2*

    Does it ever happen to you to completely blank out on the existence of a _whole construct_ of your language, and one which is just about as central to it as possible? No? Oh. Ok. #Suetum #Versu #Praxis

  41. *cone of shame, pt. 2*

    Does it ever happen to you to completely blank out on the existence of a _whole construct_ of your language, and one which is just about as central to it as possible? No? Oh. Ok. #Suetum #Versu #Praxis

  42. *cone of shame, pt. 2*

    Does it ever happen to you to completely blank out on the existence of a _whole construct_ of your language, and one which is just about as central to it as possible? No? Oh. Ok. #Suetum #Versu #Praxis

  43. Fixed some threading bugs in the debugging client - which I thought would be much harder, and instead were all decently easy to face! #Suetum #praxis #versu

  44. Fixed some threading bugs in the debugging client - which I thought would be much harder, and instead were all decently easy to face! #Suetum #praxis #versu

  45. Fixed some threading bugs in the debugging client - which I thought would be much harder, and instead were all decently easy to face! #Suetum #praxis #versu

  46. I knew I would find things to correct in the #Suetum implementation as soon as I worked on another example, but I broke my record by finding a problem before the first "start" section or the first practice completed. Yay! ... I guess. #versu #praxis

  47. I knew I would find things to correct in the #Suetum implementation as soon as I worked on another example, but I broke my record by finding a problem before the first "start" section or the first practice completed. Yay! ... I guess. #versu #praxis