Timeline for Recursive Binary Search Exit Code Errors
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 4, 2016 at 14:45 | comment | added | Ryan | Thanks again for the input, Cliff! I totally understand your critique. It was the only fix, however, that allowed me to pass the single check I kept missing. That said, as a sorta/kinda noob, return statements are less transparent to me, at least in C, than say Python. For example, I want to return a value for the system to use later, but 0 and 1 are values, and they are simply success and failure, respectively. So, I obviously need to do a bit more reading in this area. The reference you provided certainly helped. | |
| May 4, 2016 at 4:05 | comment | added | Cliff B | Interesting solution. The only problem I have with it is that it is supposed to return a bool, meaning true or false, not a value. Returning a value can get complicated as different architectures, different programming languages and different operating systems can behave unpredictably. | |
| May 4, 2016 at 2:16 | history | answered | Ryan | CC BY-SA 3.0 |