Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 29-Mar-2024 11:22:08 JST Haelwenn /элвэн/ :triskell:

   Now I'm wondering if it's a bug for FreeBSD's mktime(3) to end up setting errno to non-zero even when it really doesn't seems to have got any error (after all it doesn't returns (time_t)-1 but a correct timestamp).

   Or maybe it's just accepted that errnocan just change because side-effects.

   • Embed this notice
     tedu (tedu@honk.tedunangst.com)'s status on Friday, 29-Mar-2024 16:24:40 JST tedu

     in reply to

     @lanodan “The value of errno should only be examined when it is indicated to be valid by a function's return value.”

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 29-Mar-2024 17:05:41 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • tedu

     @tedu I'd rather it would reset errno to it's previous value (due to POSIX forbidding setting to zero) on handling the error as non-fatal though as a lot of POSIX functions return maybe-error-maybe-valid values where errno != 0 is the actual indicator of an error.