Up until now, the Petite bindings have been built around a threaded model where one thread existed solely to send new commands to the Petite process and another solely to read responses back. Mostly, this would stop the problem with the Java Process model that would cause it to deadlock if the data was not actually being consumed–the reading thread could act as a buffer in this instance.
Bug fixes:
enter in the REPL wouldn’t run the current code based on incorrect bracket matching.list->image and image->list are not properly highlighted as keywords.Two interesting things to talk about this update. First, I have my first code contribution from someone else. I’ve been working with Graham during Peer Tutoring for C212 and when we were busy, we talked about Wombat. He seemed interesting in helping, so he worked out the new about dialog for Wombat. Now it has all of the different libraries and licenses that Wombat uses, along with a nice picture.
Many thanks! (And if anyone else wants to contribute, feel free. It’s always nice to get a different viewpoint on things.)
A few minor bug fixes first:
After a long while, I’ve actually done some work on the frame displayed with draw-image. Now rather than just showing the basic image, there’s a bit of extra information available.
In the last few days I’ve managed to get a version of Scheme/Java interoperability working where Scheme code can call to Java using a side channel alongside the normal communication with the host Wombat process.
Continuing the update to the Petite back-end, I’ve rewritten the matrix library and most of the image library (everything except for read-image, write-image, and draw-image). The current code is all in Scheme, although I don’t want to write the image loading/saving code in Scheme otherwise we’ll be back into the original situation with the C211 libraries. The APIs haven’t changed though, so the previous APIs are still valid: