Hi:
On 03 Nov 2010, at 23:59, Stefan Marr wrote: > Probably our VM is behaving slightly different from what the SqueakVM. (Not > sure what the 'right' thing to do is thought) > > From my understanding, the idea is that if there is no event, the primitive > will fail. > And all other images have that case covered. They set the first array index > to EventTypeNone. > > Thus, "InputEventFetcher>>primGetNextEvent: array" should look like: > > primGetNextEvent: array > "Store the next OS event available into the provided array. > Essential." > <primitive: 94> > array at: 1 put: EventTypeNone. "STEFAN: Added this line" > ^nil > > However, since Pharo works on the other VM, I guess the primitive there is > filling in the first slot of the array anyway. > So, what is the specification? I think the primitives have changed since 'the > bluebook'. Just to ask that question again: What is the conclusion, is the bug in the image or in the VM? Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525
