Skip to content

Conversation

@ppannuto
Copy link
Member

Use of timezone in {get/set}timeofday is deprecated.

If something did try to pass us the parameter, our implementation would (incorrectly) ignore it. More significantly, our implementation does not check that the timeval struct is nonnull before dereferencing it.

This updates libtock's interface to match our implementation and the common-case scenario, and leaves the question of what to do if something tries to use the legacy tz parameter to whomever implements the wrapper.

Use of timezone in `{get/set}timeofday` is deprecated.

If something did try to pass us the parameter, our implementation would
(incorrectly) ignore it. More significantly, our implementation does not
check that the `timeval` struct is nonnull before dereferencing it.

This updates libtock's interface to match our implementation and the
common-case scenario, and leaves the question of what to do if something
tries to use the legacy `tz` parameter to whomever implements the
wrapper.
@bradjc bradjc added this pull request to the merge queue Nov 4, 2024
Merged via the queue into master with commit 7f2ced0 Nov 4, 2024
4 checks passed
@bradjc bradjc deleted the no-timezone branch November 4, 2024 23:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants