So it seems you only need VM changes integrated. How would you feel
about working directly with the vm-dev community to do this? A ticket
in the Pharo bugtracker is implicitly waiting for someone else to pick
it up and push it, but Pharo has only a few busy people to work on the
VM, thus your ticket there has languished >2yrs. There are more
non-Pharo vm-devs (who don't follow the Pharo bug tracker), so going
direct you might have a broader chance of getting it reviewed and
integrated. This might not have been so practical when you first
logged your ticket since at that time the Pharo-VM had diverged from
the mainline-Cog-VM but its now realigned to get all the Spur
goodness, so Pharo would inherit your changes in due course.
Full disclosure: I'm trying to close old tickets to reduce our
software inventory [1] - but I hopefully this is a good path for you
also.
[1] http://www.joelonsoftware.com/items/2012/07/09.html
cheers -ben
Thanks ben. You are so right :)
