Should aws_X_clock_get_ticks() return an error code?

[graebm]

Reading the kernel docs, it doesn't seem like these functions can ever fail the way we're using them.

In code we're writing that calls aws_X_clock_get_ticks(), it can be very difficult to handle situations where the clock returned a theoretical error code, so we're not bothering with thorough error handling.

Perhaps the signature should simply be: AWS_COMMON_API uint64_t aws_X_clock_get_ticks(void);

[JonathanHenson]

I tend to agree. @bdonlan thoughts?

[bdonlan]

Can we confirm if this is the case for all three major OSes we target?

[JonathanHenson]

Yes, and we checked libc++ source as well.

But embedded systems may fail so maybe we should keep it for the event loop implementations on that platform.

Sent from my iPhone

On May 24, 2018, at 11:24 AM, bdonlan [email protected] wrote:

Can we confirm if this is the case for all three major OSes we target?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.