[Vm-dev] debugging the garbage collector

Eliot Miranda eliot.miranda at gmail.com
Sat Feb 16 00:01:48 UTC 2013


On Fri, Feb 15, 2013 at 3:26 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>
> On 2013-02-16, at 00:20, tim Rowledge <tim at rowledge.org> wrote:
>
>> On 15-02-2013, at 3:13 PM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>>>
>>>
>>> So should we keep the backward-compatible, but incorrect signatures,
>>> and hack the VMMaker source to comply with them, or change the
>>> signatures and risk breaking plugin and support code?
>>
>> The SVN code tree should be updated. Anything affected should be corrected. Different vintage code should not be mixed and so there surely ought not be any backward compatibility issue.
>
>
> Well, in the Real World (TM) mixing and matching does happen. E.g. Scratch on Linux does ship with a couple of binary plugins while relying on the system-provided VM. It's rather likely the two were not compiled from the exact same sources. The interpreter proxy versioning was designed to allow this version mismatch of binary plugins to still work.

Right.  But the change in signature won't break anything because those
return values are not used.  Right?

>
> - Bert -
>
>



-- 
best,
Eliot


More information about the Vm-dev mailing list