fredag 26 november 2010
The VMProcess implementation in the GNU CP is kind of aimed at *nix-processes using fork and reap and such. The Process.java implementation is relatively easy and actually more coherent with the Amiga-way of handling processes. So, a JAmiga-native VMprocess-class is probably the best route to go. Should lead to fewer internal/extrnal lists for JAmiga-processes, allowing us to use the Amiga processlists directly.
måndag 22 november 2010
It seems that my version of the VMCPStringBuilder.class was erronous, or rather; it was probably compiled to have native functionality implemented -- which I haven't bothered with.
So. Progress. I have managed to run a few Process-related stuff, and I'm about to take a look a the Ctrl-C-handling in the Object.wait()-method. This, so any galloping processes (such as my mauve-tries) can be breaked, without JAmiga going down (which is what happens now).