Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Contribute to GitLab
  • Sign in
P
paho.mqtt.c
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • eclipse
  • paho.mqtt.c
  • Repository

Switch branch/tag
  • paho.mqtt.c
  • src
  • samples
  • MQTTAsync_publish.c
Find file
BlameHistoryPermalink
  • Guilherme Maciel Ferreira's avatar
    Using standard constant for exit(3) and return · 32e8eaa2
    Guilherme Maciel Ferreira authored Apr 17, 2016
    According to ISO/IEC 9899:2011, section 7.22.4.4 (The exit function),
    "the constant EXIT_FAILURE is the implementation independent way to
    issue failures to exit(3)." Whereas EXIT_SUCCESS is the standard way
    to return success. Favor this platform independent constants than the
    literal numbers.
    Signed-off-by: 's avatarGuilherme Maciel Ferreira <guilherme.maciel.ferreira@gmail.com>
    32e8eaa2
MQTTAsync_publish.c 3.9 KB
EditWeb IDE

Replace MQTTAsync_publish.c

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.