Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Never invoke exit(3) within library implementation #8

Merged
merged 1 commit into from
Mar 16, 2018
Merged

Never invoke exit(3) within library implementation #8

merged 1 commit into from
Mar 16, 2018

Commits on Mar 16, 2018

  1. Never invoke exit(3) within library implementation 

    It is dangerous and irresponsible to invoke exit(3) in a certain library
consisting of several functions. Outer developers would never understand
why their programs exit when linking to dcurl. Instead, we should always
ensure the appropriate return values and transit state machine
internally.

TODO: the following files are not changed accordingly because function
prototypes have to be modified in order to reflect return values:
  * src/clcontext.c
  * src/pow_cl.c
  * src/dcurl.c
    @jserv
    jserv committed Mar 16, 2018
    Configuration menu
    Copy the full SHA
    04fb126 View commit details
    Browse the repository at this point in the history