From cd0c502986c8547bf6823811f234f7a6cc365de2 Mon Sep 17 00:00:00 2001 From: Mathieu Lacage Date: Thu, 24 May 2007 09:22:48 +0200 Subject: [PATCH] more dox improvements --- src/simulator/nstime.h | 4 +++- src/simulator/simulator.h | 10 ++++++---- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/src/simulator/nstime.h b/src/simulator/nstime.h index 774b2ba79..2958f2f3e 100644 --- a/src/simulator/nstime.h +++ b/src/simulator/nstime.h @@ -448,7 +448,9 @@ private: * * This is an instance of type ns3::TimeUnit<1>: it is * the return value of the ns3::Simulator::Now method - * and is needed for the Simulator::Schedule methods + * and is needed for the Simulator::Schedule methods. + * The precision of the underlying Time unit can be + * changed with calls to TimeStepPrecision::Set. * * Time instances can be created through any of the following functions: * - ns3::Seconds diff --git a/src/simulator/simulator.h b/src/simulator/simulator.h index 1f7799d0c..c30b43661 100644 --- a/src/simulator/simulator.h +++ b/src/simulator/simulator.h @@ -37,11 +37,13 @@ class SchedulerFactory; * \brief Control the scheduling of simulation events. * * The internal simulation clock is maintained - * as a 64-bit integer in nanosecond units. This means that it is + * as a 64-bit integer in a unit specified by the user + * through the TimeStepPrecision::Set function. This means that it is * not possible to specify event expiration times with anything better - * than nanosecond accuracy. Events whose expiration time is - * the same are scheduled in FIFO order: the first event inserted in the - * Scheduling queue is scheduled to expire first. + * than this user-specified accuracy. Events whose expiration time is + * the same modulo this accuracy are scheduled in FIFO order: the + * first event inserted in the scheduling queue is scheduled to + * expire first. * * A simple example of how to use the Simulator class to schedule events * is shown below: