Hi, Some food for thought.
Given the (minor?) fallout, I wonder if we should have instead just added a distinct numerical value for CLOCK_BOOTTIME, which didn't occur to me while doing the review. This would have the benefit of allowing all these 'case' labels to coexist, which makes the interface more predictable and thus easier on applications. The patches below obviously only can cover the precise applications that we noticed failed to compile, and not other existing ones nor future ones to be written. I don't see any real drawback for such an approach because, to read clock information, applications always have to specify the clock ID and, AFAIK, cannot, e.g., request a list of clocks and times, where we would have to be careful to output the same time for all the aliased clock IDs. Thanks. -- Olivier Certner
signature.asc
Description: This is a digitally signed message part.
