Hi Everyone, I am running into some issues integrating thrift into an existing build process. The source of the problem lies in the fact that thrift headers inline a large portion of the code. Specifically, TPipedTransport calls malloc, realloc and free in the header. This becomes a problem in existing builds when custom memory allocation is instrumented using linker redirection (ld --wrap)
I would like to gauge the community reaction to a potential patch that would move code that performs memory management into the ".cpp". I would also be interested in hearing if there are any reasons other than potential performance gains for keeping this type of code in the headers. Thanks, Anatoly
