well I cant see what your "problem" is without a real world example, byteptr works *very* well as is, in fact its invaluable!
And it'll be just as invaluable if you have to explicitly cast to it. I'm not asking to remove the ability, only to enforce explicit casting, so you don't do it by mistake. I'm surprised wrapping Ogre hasn't demonstrated the problems with the current situation, but maybe you're wrapping very differently to how I do.
His problem is mainly that it implicitely casts to Byte Ptr, without needing a Byte Ptr(sometypethingy) ...
Precisely!
I would suggest that this is changed, at least in superstrict, so you need to explicitely cast everything that is casted somewhere ... (I'm only using strict, so I don't mind much)
Again, precisely! Leave it alone in Strict and non-Strict, no need to penalize users who don't want strict error checking, but SuperStrict implies that I want all my mistakes pointed out and that I have to declare my intentions at every stage.