🤔 are these exit codes random or do they have meaning ❓

[reactive-firewall]

🤔 are these codes random or do they have meaning ❓
- is that meaning documented? where? (nope not documented....yet)

Originally posted by @reactive-firewall in #11 (comment)

• document it somewhere

[reactive-firewall]

Following the scaling principle of "there is only 3 useful quantities for things: none, one, or many" leads to the following base definitions:

required return code meanings

For Multicast Project

• 0 is the default and implies success, and means the process has essentially (or actually) returned nothing (or None)
• 1 is used when a single result is returned (caveat: functions may return a single tuple instead of None to indicate exit code 1 by returning a boolean success value, and result (which may also be encapsulated as an iteratable if needed) )
• 2 is used to indicate a value and reason are returned (caveat: functions may return a single tuple with a single value and reason and the value can be a tuple)
• -1 is used to mean many of unspecified length and otherwise functions as 1

required CLI exit code meanings

Also for Multicast Project

• 0 success
• 1 none-sucsess - and is often accompanied by warnings or errors
• 2 > failure of specific reason

Everything Else exit code meanings

not important to Multicast Project

Other codes (such as 126) may or may not have meanings (such as skip) but are not handled within the scope of the Multicast Project at this time.

[reactive-firewall]

🤔 posix exit codes are zero for no-error and non-zero for errors but also limit max exit code to 255.

🤔 also consider common linux exit codes

• should support codes like 128+N and 2 where possible