> (2) The update_nb option seems to take great care to avoid calling
> getmilliseconds() on every loop. Is there a particular system that
> this call is very expensive on?
Olivier,
I've done a quick test on Linux and Windows and found that it is quite
fast (395/390 nanoseconds), certainly compared to some of the heavy
lifting that the main processing has to do. It seems that this is cheap
enough that removing the up_nb option, or at least making the default
behavior to get the time more often (e.g., every loop and call to
call::run()) would be a good idea. If you agree, I'll work up a patch to
that effect.
Charles
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
