On Thu, Nov 26, 2015 at 12:09 PM, Luca Barbato <[email protected]> wrote: > On 26/11/15 17:31, Ganesh Ajjanagadde wrote: >> IMHO uglier than just using casts. Same remark applies to other such things. > > The pros in using this approach is that is easier to spot, the cons is > that it is easier to spot. > > All in all, I'd rather mark clearly code that is borderline than just > using casts (that w/out the last patch do not silence the warnings btw). > > Currently a normal build has about 500 warnings, as Courmish stated many > times having _that_ many warnings is just hiding problems. > > As long we can manage to drop all the warnings that are not real > problems I'm happy.
Ok. I was mostly saying this from a merge perspective (increased merge load), and my own work on warning suppression. Anyway, I don't mind. > > lu > _______________________________________________ > libav-devel mailing list > [email protected] > https://lists.libav.org/mailman/listinfo/libav-devel _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
