>>4,5
LOL! This is C++, not Java, you don't have to worry about fucking up with pointers here. I even did some hardcore pointer manipulation (before refactoring it into a scalable enterprise solution using industry standard best practices) without fucking up in more than one place, and that was only an OOB of one byte, which I discovered after using Valgrind. The program didn't crash, of course.