Hi, On Sun, 2013-12-22 at 23:41 +0100, Tommi Mäkitalo wrote: > I don't really see a good solution for that, other than keeping > everything as it is. Any ideas?
timeout() could return WeakTimespan<Timespan::Milliseconds>, instead: template<typename Resolution = Timespan::Microseconds> class WeakTimespan; Add a operator int64_t that is specialised for each Resolution and allow a Cast to Timespan. Still not perfect but would allow a transition to a more typesafe interface. unsigned timeoutMs = client.timeout(); //still works cxxtools::Timespan timeout(client.timeout()); //would be correct no matter what resolution client.timeout() returns. Regards, Julian ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
