LibPhenom, a high-performance C eventing framework from Facebook

Re:LibPhenom, a high-performance C eventing framework from F... by wezfurlong on Monday September 16, 2013 @04:52PM (#6395828)

I'm not hot for reimplementing printf, but I did need an interface that made it easy to print diagnostics for various objects; rendering them to the stack and then passing them to the underlying printf implementation makes for a lot of boilerplate code.

In addition to reducing boilerplate and aiding portability, having our own printf implementation aids in consistent behavior across platforms, and allows for a deeper integration with our streams and buffers so that we don't need to make a series of clunky calls to measure how much storage is needed before passing the formatted data into the lower layers.

[ Parent | on HN ]

Re:LibPhenom, a high-performance C eventing framework from F... by codehero on Monday September 16, 2013 @05:03PM (#6395892)

I know the scope of your project isn't to break ground on formatted output. I've seen the same thing you've done in fastcgi. and in nginx. A pattern that recurs because printf is a clunky interface. And of course each copy has its own little syntax variation. But people accept the printf approach because they were indoctrinated, starting from "Hello World". I know there's something better out there.

[ Parent | on HN ]

Re:LibPhenom, a high-performance C eventing framework from F... by TheZenPsycho on Monday September 16, 2013 @08:47PM (#6396904)

You know there's something better? What is it?

[ Parent | on HN ]