Correctly bubbling exit-codes

[dsoprea]

It looks like CLAP methods often return integers, which I can only assume represent exit codes, and yet any integers returned by the verb handlers will seemingly be ignored (with the process always returning (0)).

I see that there was an issue for this in 2012: #12. Is there support yet for the user-defined handlers to return non-zero rather than either conceding just (0) or (1) to represent error state or just doing an Environment.Exit(x) manually?

Thanks.

[adrianaisemberg]

CLAP does not support exit-codes. That's a good ides!
You are welcome to submit a pull-request with such support ;)

Regards,
Adrian

Adrian Aisemberg

Get Tapet for Android
https://play.google.com/store/apps/details?id=com.sharpregion.tapet

On Fri, Jul 8, 2016 at 7:15 PM, Dustin Oprea notifications@github.com
wrote:

It looks like CLAP methods often return integers, which I can only assume
represent exit codes, and yet any integers returned by the user-defined
subcommand handlers will seemingly be ignored (with the process always
returning (0)). Is there actually support for the user-defined handlers to
return non-zero?

Thanks.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#41, or mute the thread
https://github.com/notifications/unsubscribe/AA0VhhxyPj415ZH3Tw2LS0UFVItpaR8bks5qTwQ-gaJpZM4JIhPX
.

[dsoprea]

This is still in my queue, to investigate.