On Jun 29, 2013, at 7:54 AM, Tom Browder wrote: > The SafeFormat functions are: FPrintf, Printf, and SPrintf, mimicking > C's fprintf, printf, and sprintf, but with better type safety. > Another advantage is that, for FPrintf, the output can be to either C > file pointers or C++ ostreams, which helps immensely when porting old > C code to streams incrementally.
Since this falls squarely in LIBBU's domain, what would be the value? There doesn't seem to be any integration issues, but I'm having trouble seeing how they'd be put to use... We cannot expose C++ constructs in the LIBBU API (as it is a C API), so the SafeFormat functions would end up being implementation detail behind some wrapper like bu_log() or bu_vls_vprintf()... which already work very well. I have looked at Loki for some other things, but I actually believe there are several constructs that we do much better in our core libraries. Some not as well, but features we don't use. Cheers! Sea ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
