On Oct 20, 2013, at 4:59 PM, Nicholas Reed <[email protected]> wrote: >> %V: Nicholas votes yes. Personally, I don't thinks it's justified. > I'm not going to lose sleep if it goes away, but what exactly is the > cost of keeping it? It's already implemented and working and used in a > hundred different places. It seems to me like changing all the > existing usages just so that you can be left with the exact same > behavior is like substituting every "they're" with "they are". Sure, > nothing is really lost in the translation, but nothing is gained > either, so why bother?
If we had a perfect "grammar error detector" but that only worked sans apostrophe, it might be worth it. Especially with habitually bad writers... :) Since %V is really our only customization of the format string on non-windows platforms, there is a potential benefit of being able to enable, catch, and fix -Wformat-strings warnings. That said, I'm completely ambivalent on this one because I think it's a wash: customized API, brief code, and no validation or standard API, longer code, but with validation Cheers! Sean ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
