Another note on the static variable, the name "is(..)Robot" implies it's meant to describe the state of a single instance of a class, while in most languages static would make it the same for all instances.
IE in c# you may have
public static bool IsKillerRobot { get; private set; }
Which would be as safe as any other property, but when a single robot is meant to turn killer, all of them would
Another note on the static variable, the name "is(..)Robot" implies it's meant to describe the state of a single instance of a class, while in most languages static would make it the same for all instances.
IE in c# you may have
Which would be as safe as any other property, but when a single robot is meant to turn killer, all of them would
Presumably we are in the runtime of a single robot, not a manager handling an arbitrary number of them, but I see what you mean.
Fair point, seems I forgot programming is still limited by physical boundaries :-P
Yup, this is how you get hacks like this:
rust-embedded.github.io/book/perip...