On 14/10/13 18:49, Diego Biurrun wrote: > I've used it successfully on some of the largest files in libav, e.g. > h264.c, so I really don't know what you are talking about... >
You can run it function by function and put some changes on top and even in that case you might miss something. Sometimes you do not run it on certain code because fixing it after takes more time. On top of it uncrustify isn't a C parser so it can misinterpret and generate faulty code that by sheer unluck compiles, happened before and can happen later. Thus why clang-format might be a better pick (or cparser-format once they get to that point) lu _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
