Just added a GitHub action to my CLIPSmqueue repo[1] that runs the full test suite when new commits are pushed. Seeing that little green checkmark next to the commit message is so satisfying.
Just added a GitHub action to my CLIPSmqueue repo[1] that runs the full test suite when new commits are pushed. Seeing that little green checkmark next to the commit message is so satisfying.
Today I published a JSON parser written in COOL, CLIPS's Object Oriented Language: https://github.com/mrryanjohnston/COOLJSON
This is the culmination of a few years of learnings and plenty of failed attempts along the way. Feels good to get something working finally :)
I am beginning to favor 'explicit' over 'implicit' programming.
No guesswork. Limited risks.
You know exactly what you're in for.
Don't play Plinko with data.
Be explicit.
I wrapped #raylib with CLIPS! Check it out:
https://github.com/mrryanjohnston/CLIPSraylib
CLIPS and raylib are really incredible and work so well together.
A loop I made tonight in CLIPS:
https://gist.github.com/mrryanjohnston/2062ba2cba820d391cfe2ddfb88d028d
It provides an "environment-as-linked-list," allowing you to iterate through elements in a linked list `n` number of times by running the environment with `(run n)`.
It uses a single `deftemplate` and `defrule`. We use nested `assert`s to "link" meta-facts together.