Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.

We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.

Thank you for your understanding.

  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 22 subscribers
  • Views 2704 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

mktime behaviour

Stefan Hartwig

Hi,
I use mktime to convert date and time into a time_t value and I see a behavior, which I didn't expect.
When calling mktime with 29.02.2010, I would expect the function to return -1, but it returns a time_t value representing the 01.03.2010.

Is that the normal behavior?

Parents
  • 0

    It's normal that it normalizes the parameters.

    From §7.23.2.3 of ISO/IEC 98:99:1999:
    "The original values of the tm_wday and tm_yday components of the structure are ignored, and the original values of the other components are not restricted to the ranges indicated above."

    This is what a Linux system writes about mktime():
    "If structure members are out-side their legal interval, they will be normalized (so that, e.g., 40 October is changed into 9 November)."

Reply
  • 0

    It's normal that it normalizes the parameters.

    From §7.23.2.3 of ISO/IEC 98:99:1999:
    "The original values of the tm_wday and tm_yday components of the structure are ignored, and the original values of the other components are not restricted to the ranges indicated above."

    This is what a Linux system writes about mktime():
    "If structure members are out-side their legal interval, they will be normalized (so that, e.g., 40 October is changed into 9 November)."

Children