add config option to make absolute_time_t always a uint64_t #729

Closed
opened 2022-02-10 09:00:53 -06:00 by kilograham · 4 comments
kilograham commented 2022-02-10 09:00:53 -06:00 (Migrated from github.com)

The intention was that people would always use the macros (e.g. to_us_since_boot, so the difference in implementation would not matter.

As stated in the docs the reason for making absolute_time_t a separate type was to avoid confusion between timeouts and longs.

Frankly, if people were using the macros, it is probably fine to make the default be that everything is a uint64_t.

The intention was that people would always use the macros (e.g. `to_us_since_boot`, so the difference in implementation would not matter. As stated in the docs the reason for making absolute_time_t a separate type was to avoid confusion between timeouts and longs. Frankly, if people were using the macros, it is probably fine to make the default be that everything is a uint64_t.
noname22 commented 2023-11-11 05:18:52 -06:00 (Migrated from github.com)

As stated in the docs the reason for making absolute_time_t a separate type was to avoid confusion between timeouts and longs.

Where is this explained in the documentation? I can't find any explanation of the rational behind this.

> As stated in the docs the reason for making absolute_time_t a separate type was to avoid confusion between timeouts and longs. Where is this explained in the documentation? I can't find any explanation of the rational behind this.
kilograham commented 2024-07-07 12:48:53 -05:00 (Migrated from github.com)

it is in the doxygen for the type

it is in the doxygen for the type
lurch commented 2024-07-07 18:24:48 -05:00 (Migrated from github.com)
...which can be seen online at https://www.raspberrypi.com/documentation/pico-sdk/group__timestamp.html#rpip6054cfaa87d222c22077
kilograham commented 2024-07-07 18:57:46 -05:00 (Migrated from github.com)

but yes we will make this off by default

but yes we will make this off by default
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-raspberrypi/pico-sdk#729
No description provided.