On Fri, Jul 29, 2011 at 3:11 AM, Larry Gritz <[email protected]> wrote: >> One of the versions of tfm::format() is source compatible with OIIO's >> Strutil::format() so I found that as a quick hack, doing a >> >> using tinyformat::format; >> >> inside namespace Strutil and commenting out the old format seemed to compile >> ok. It also seems to work ok, judging from the output of iv's >> updateStatusBar() >> function. > > Exactly. But the problem is that if you do this when variadic templates are > available but stick to the old implementation when they aren't, you end up > restricting yourself to only using the usual POD types, leaving on the table > most of the interesting functionality of tinyformat.
This isn't what I'm suggesting - if you ever need to swap tinyformat out for printf() then you're totally blowing the ability to do anything interesting with the type safety. What I meant by the above was that I'd compiled OIIO *in the usual C++98 mode* using tinyformat's C++98 support. Really, it's not that bad only defining all the versions up to some maximum number of arguments - this is exactly what boost does for types like boost::tuple. ~Chris _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
