Seperate real and user timer interfaces

Use more descriptive names, and make it clearer that real and user
timers work on different static storage.  The end goal is to be able to
reuse those timer functions, instead of inlining other timer
implementations subject to clock jumps.

Discussed with Scott Cheloha

1 files changed, 4 insertions, 10 deletions

diff --git a/src/usr.bin/openssl/apps_posix.c b/src/usr.bin/openssl/apps_posix.c
index 94c6d35f71..502919c0a2 100644
--- a/src/usr.bin/openssl/apps_posix.c
+++ b/src/usr.bin/openssl/apps_posix.c
@@ -123,8 +123,8 @@
 
 #include "apps.h"
 
-static double
-real_interval(int stop)
+double
+app_timer_real(int stop)
 {
         static struct timespec start;
         struct timespec elapsed, now;
@@ -138,8 +138,8 @@ real_interval(int stop)
         return 0.0;
 }
 
-static double
-user_interval(int stop)
+double
+app_timer_user(int stop)
 {
         static struct timeval start;
         struct timeval elapsed;
@@ -154,12 +154,6 @@ user_interval(int stop)
         return 0.0;
 }
 
-double
-app_tminterval(int stop, int usertime)
-{
-        return (usertime) ? user_interval(stop) : real_interval(stop);
-}
-
 int
 setup_ui(void)
 {