A good explanation of top-down operator precedence parsing. An elegant and flexible technique… odd that it’s not more common.

From the same author, an explanation of byte stuffing. I’ve implemented this a few times. It’s elegant but suffers from data-dependent encoding size, an annoyance if you need consistent timing. If you don’t care about timing then you could hardly do better for a generic packet encapsulation over an unreliable byte stream.

C++ FQA Lite. I think the snark is well warranted, particularly regarding the abomination that is iostreams. <<? “Manipulators”? Come on now. Type-safe it may be, but it just looks like hell.