On Sat, May 24, 2014 at 1:29 AM, David T. Lewis le...@mail.msen.com wrote:
On Fri, May 23, 2014 at 10:26:54PM +0200, Stephan Eggermont wrote:
David wrote:
In any case, the change affects one source file in the VM platform
sources, so if you can arrange to get that included in the Pharo VM
Thanks, David.
Where do I find a precompiled cog vm with the changes to test with? (preferably
mac,
but linux will do). build.squeak.org doesn't seem to have a recent green build.
Stephan
Hi Stephan,
The precompiled Cog VM would need to come from Eliot's site (or follow the
links to Eliot's site from http://squeakvm.org). The build.squeak.org job
is really just me testing the VMMaker code generation, it's not intended
as a source of VMs.
I tested Eliot's change and it works, but
Ok, I created a pull request on https://github.com/pharo-project/pharo-vm.
I guess there should be a way to use the diff directly, instead of editing the
file by hand.
Stephan
David wrote:
In any case, the change affects one source file in the VM platform
sources, so if you can arrange to get that included in the Pharo VM
builds, that should provide a working VM that you can use for OSProcess on
Pharo.
I noticed that this is only a unix vm change. Should this be
On Fri, May 23, 2014 at 10:26:54PM +0200, Stephan Eggermont wrote:
David wrote:
In any case, the change affects one source file in the VM platform
sources, so if you can arrange to get that included in the Pharo VM
builds, that should provide a working VM that you can use for OSProcess on
PetitParser 1.6 instead of 1.5.
Tests only work when no Nautilus browser is open. Some notification problem
when creating classes.
OSProcess ci has lots of failing tests, so we don't know if it actually works…
Diego Stephan
Verstuurd vanaf mijn iPhone
