> It's 2015. One should not be hand-coding string manipulation at the pointer level. True, although that was building a binary message, not exactly a string.

> It's 2015. One should not be hand-coding string manipulation at the pointer level. True, although that was building a binary message, not exactly a string. "frame" should have probably been a (packed) struct instead of "unsigned char frame[256];".