> Assuming you're agreeable to adjusting the code to avoid alloca, we'll > do a quick turnaround on the v3 -- I'll just audit the return paths to > make sure we don't leak and we'll be good to go.
Thanks for point out that, let me figure out which is the best way to fix that, using xstrdup + free or some other smart pointer from C++ :P
