Peter's Notebook

chekc; monad defintion bound/free/named variables in loop descriptions I had a stupid idea that’s working out so well I love it.1 I’m trying to translate JVM bytecode into a tree. This won’t always work but for most (or all of my) side-effect-free cases; it should be fine.2 Okay … so how does one (such as I) do that? Well … the bytecode encodes a series of operations against “the stack” and “the local variables” - hereafter stack and store.

This is a quick post-mortem on the three methods I examined for nesting some of our Git repos. In the end, I ran out of time and felt that the diversity of a CS team means that special handling would not produce a time saving benefit for me. submodule Git’s (somewhat) anointed solution is “submodules” and comes built in. Google’s CORGI project (et al) use it. trial I created two shared repositories and a third master repository.

p-Unity is/was/will-be a dumping ground for stuff I’ve written in Scala/Gradle to automate the parts of Unity3D that I wish to automate. For now; it’s a (twitchy) way to run editor tests from the command-line. Once/when I assemble re-usable packages, I’ll be able to fill in the stubs and make it; - build pre-compile assemblies from src/(main|test)/punity/ in Gradle-Like fasion. - publish/consume code as Gradle dependencies - export packages from the command line - export players from the command line

Source mirror; https://github.com/g-pechorin/sstate.scala Won’t actually build, use the full repository here Releases (tags) https://github.com/g-pechorin/sstate.scala/tags "com.peterlavalle" %% "sstate" % ??? 'com.peterlavalle:sstate_2.12:???' SState SState is a cute little pure-functional FSM class in Scala that I wrote after seeing JEasyStates. The only real advantage of mine is that it can (probably) be dropped into a Scala.JS project without any magic. There’s a unit test at the foot of this doc showing how I test it.

I got super mad at a long running git task. It was taking non-trivial time to checkout and push between repositories. I couldn’t find docs for a (working) git command sequence1 that pushed branchesfrom one remote to another; so I wrote a python script to checkout a branch to local then push it. Once I was sure that it was running; I could reallocate my attention to something more deserving of my talents.

This is just a “victory dance” sort of post about setting up a multi-branch build, for a Mercurial project, from a JenkinsFile. When I first tried to do this sthing, I recieved a message reading; ERROR: No configured Mercurial installation which was annoying. I hadn’t needed to setup Mercurial before, why did I need to now? Turns out, the workaround/worksforme from here this bug solves the problem by defining the default Mercuiral setup as … the … default?

Scala’s extractors and unapply() represent a concept that I haven’t grok’ed until now. Most demonstrations seem to be too long or use the same types everywhere. Here are my thoughts on the concept; val a: C = ??? val i: I = ??? i match { case a(f: O) => ??? } This will try to call the below method class C { def unapply(i: I): Option[O] = ??? } There’s some more flexibility;

I made a semi-cache coherent container which provides an Entity-Component-System. These are the bones of contemporary game-engines. This post is a bit crude; I keep thinking about it then adding features to Whippet instead of writing this up. Whippet on GitHub Google built CORGI which isn’t (yet?) trying to act cache coherent. It also is more than trivial to build, and suffers from NIH for me. Actually; that last bit isn’t likely to be a problem form most, but I didn’t like their license.

I made a semi-cache coherent container which provides an Entity-Component-System. These are the bones of modern game-engines. This post is largely a gooey weasel opinion piece. It started as an introduction that grew out of control. So, for now, it’s just a bit of rambling while I clean-up the documentation for my tool. Of Entity-Component-Systems Among other things, Jason Gregory’s book Game Engine Architecture discusses the concept of a data-driven architecture for game software.

Have you used TortoiseHG? It is lovely! Have you used Cmder? It is lovely! If you … setup cmder to launch from the command line open TortoiseHG Workbench > File / Settings > TortoiseHG / Shell put cmder %(root)s into the Shell field … then you can have these two lovely tools holding hands and kicking-bugs!