On Tue, Sep 15, 2020 at 01:17:41PM -0700, tim Rowledge wrote:
> 
> 
> > On 2020-09-15, at 1:12 PM, David T. Lewis <lewis at mail.msen.com> wrote:
> > 
> > This was the first issue that popped up when I put a halt in eventMillisecondClock.
> > 
> > I see a number of other senders of eventMillisecondClock that handle the case
> > of an event buffer with time stamp of 0. Is that even possible?
> 
> I wrote about some of those last week; I suspect that the idiom was there because some very early VM stuff couldn't provide the time stamp. Certainly shouldn't be the case any longer and I'd be inclined to remove them all.
>

Yes thanks, sounds right.

This one was kind of a trivial change, but it seemed to be the most common use
of eventMillisecondClock in practice, so it seemed worth a commit to make it
go away.

Dave