Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G GLib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 862
    • Issues 862
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 39
    • Merge requests 39
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • GLib
  • Repository
Switch branch/tag
  • glib
  • gio
  • tests
  • gdbus-example-unix-fd-client.c
Find file BlameHistoryPermalink
  • Philip Withnall's avatar
    glib: Don’t use time(NULL) to get current time · 92e05928
    Philip Withnall authored Jul 06, 2018
    Use either g_get_real_time() or g_date_time_new_now_local(). This means
    we don’t need to worry about time_t being 32b in future (the year 2038
    problem), and it makes the need for error handling a bit more explicit.
    Improve the error handling in several cases.
    
    Based on a patch by Niels De Graef
    (!142
    
    ).
    
    Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
    
    #1402
    92e05928