char buf[LINE_MAX]

Why do programmers still code in arbitrary limits like these?

It breaks when you do
#define LINE_MAX UINT_MAX

Why not redesign so that you use an O(1) space algorithm, or if it can't be avoided, dynamically allocate as much as needed?

>>32
Have you never written real code before?  The easiest is a continuation, but in C or ENTERPRISE OO TUR_^NKEY SOLUTIONS you encapsulate the state of processing in an object (you know, just those same damn variables you'd have bound up inside your OMG OPTIMIZED parsing loop) and hop right back where you left off when more data comes in.  You don't even need a full state machine, though if you're generating those or have a protocol generator it's the easiest.

Fuck, you people are inexperienced.