Timeline for 1, 2, 3, 4, 5, Shaggy
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2020 at 9:04 | history | edited | CommunityBot |
Commonmark migration
|
|
| Nov 4, 2016 at 17:01 | history | edited | ElPedro | CC BY-SA 3.0 |
added 10 characters in body
|
| Nov 4, 2016 at 16:49 | history | edited | ElPedro | CC BY-SA 3.0 |
added 92 characters in body
|
| Nov 4, 2016 at 0:35 | comment | added | ElPedro | Explanation added to my answer for info. | |
| Nov 4, 2016 at 0:25 | history | edited | ElPedro | CC BY-SA 3.0 |
added 190 characters in body
|
| Nov 3, 2016 at 23:54 | comment | added | ElPedro | My pleasure. Always happy to (try to) explain :) | |
| Nov 3, 2016 at 23:49 | history | edited | ElPedro | CC BY-SA 3.0 |
added 8 characters in body
|
| Nov 3, 2016 at 23:42 | history | edited | ElPedro | CC BY-SA 3.0 |
added 16 characters in body
|
| Nov 3, 2016 at 23:36 | comment | added | ElPedro |
Basically it means that c starts with a default value of 1 and I just add 1 to it every time I call the function while c<a
|
|
| Nov 3, 2016 at 23:32 | comment | added | ElPedro | The function call is f(a,b). c defaults to 1 because of the c=1 in the function definition. That means I can use c in the first run without having to add it to the function call (Python functions accept optional keyword args). I can then increment it on the recursive function calls and its value on the recall overrides the default. Hope that makes it clear. Took me a while to get to grips with it :) | |
| Nov 3, 2016 at 23:27 | comment | added | nedla2004 | Am I confused, or do you never need to assign to c? | |
| Nov 3, 2016 at 23:24 | history | answered | ElPedro | CC BY-SA 3.0 |