mirror of
https://github.com/zeek/zeek.git
synced 2025-10-11 02:58:20 +00:00
Event: Use -1.0 for undefined/unset timestamps
This can happen if either there's no network timestamp associated with an event, or there's currently no event being dispatched. Using 0.0 isn't great as it's the normal start timestamp before reading a network packet. Using -1.0 gives the caller a chance to check and realize what's going on.
This commit is contained in:
parent
e2e13902f3
commit
7b4b1779bf
5 changed files with 29 additions and 4 deletions
|
@ -49,6 +49,8 @@ using EventMetadataVectorPtr = std::unique_ptr<EventMetadataVector>;
|
|||
*/
|
||||
EventMetadataVectorPtr MakeEventMetadataVector(double t);
|
||||
|
||||
constexpr double NO_TIMESTAMP = -1.0;
|
||||
|
||||
} // namespace detail
|
||||
|
||||
class Event final : public Obj {
|
||||
|
@ -170,8 +172,8 @@ public:
|
|||
// the event was intended to be executed. For scheduled events, this is the time the event
|
||||
// was scheduled to. For any other event, this is the time when the event was created.
|
||||
//
|
||||
// If no event is being processed, returns 0.0.
|
||||
double CurrentEventTime() const { return current ? current->Time() : 0.0; }
|
||||
// If no event is being processed or there is no timestamp information, returns -1.0
|
||||
double CurrentEventTime() const { return current ? current->Time() : detail::NO_TIMESTAMP; }
|
||||
|
||||
int Size() const { return num_events_queued - num_events_dispatched; }
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue