OK, you got me there. That's probably the only good reason you could  
possibly have a need for a prim number!

I suggest using 169, next to primitiveCopyObject - at least for now.  
You will, of course, be making your design so nicely factored and  
intelligible that it could be changed at any time without causing a  
problem, won't you :-)

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: HALT: No-Op