[Vm-dev] Re: Need a marker primitive

timfelgentreff timfelgentreff at gmail.com
Wed Apr 29 22:19:42 UTC 2015


And it seems I botched the merge. Vmmaker-tfel.363 should fix that. In any
case, the diff should have been this:

  ----- Method: InterpreterProxy>>primitiveFailFor: (in category 'other')
----- 
  primitiveFailFor: reasonCode 
+ "Set specific primitive failure. N.B. primitiveFailFor: PrimNoErr is
expected to clear the primFailCode. 
+ Primitive 255 is called to indicate that we are currently simulating a
primitive that should fail and the VM should handle that case appropriately
(if supported by the VM)." 
+ <primitive: 255> 
+ ^ primFailCode := reasonCode! 
- "Set specific primitive failure. 
- N.B. primitiveFailFor: PrimNoErr is expected to clear the primFailCode." 
- ^primFailCode := reasonCode! 

Item was changed: 
  ----- Method: InterpreterProxy>>success: (in category 'other') ----- 
  success: aBoolean 
  self failed ifTrue: [^ self]. 
  aBoolean ifFalse: [ 
+ self primitiveFailFor: 1. 
- primFailCode := 1. 
  (self confirm:'A primitive is failing -- Stop simulation?') ifTrue:[self
halt]] 
  ! 




--
View this message in context: http://forum.world.st/Need-a-marker-primitive-tp4821675p4823042.html
Sent from the Squeak VM mailing list archive at Nabble.com.


More information about the Vm-dev mailing list