[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
timevar: further work
From: |
Bruno Haible |
Subject: |
timevar: further work |
Date: |
Sun, 30 Sep 2018 01:18:51 +0200 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-134-generic; KDE/5.18.0; x86_64; ; ) |
Hi Akim,
- Unclear comments: timevar_enabled: When does it need to be set? Before or
after init_timevar() is called?
- Portability: According to the Gnulib documentation, 'times' is missing on
native Windows (mingw, MSVC). The Gnulib module 'times' has a replacement for
it, that is better than the clock() fallback. How about making 'timevar'
depend on the Gnulib module 'times'? Then you can ditch at least the
USE_CLOCK code.
- Is the 'times' approach preferrable to the 'getrusage' approach in all
cases? I'm thinking of multithreading and of processes that fork() children.
Bruno
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- timevar: further work,
Bruno Haible <=