Comment on Why does the for loop repeat in this recursion?

• jrbaconcheese@yall.theatl.social ⁨10⁩ ⁨months⁩ ago

  No, the moment that draw(9) is called, draw(10) goes on pause while draw(9) finishes… which repeats (or recurses) until draw(0) gets called. Then it _return_s which returns to draw(1). The draw(1) un-pauses and does the #\n bit and returns to draw(2), which un-pauses and does ##\n and so forth until draw(10) does ##########\n

  source

  • milon@lemm.ee ⁨10⁩ ⁨months⁩ ago

    Gotcha. Thanks for the explanation.

    source
• mac@programming.dev ⁨10⁩ ⁨months⁩ ago

  When the draw function calls itself it yields control to that new function its calling. When that function ends it takes back control and continues doing what it was doing.

  This means all of the for loops in all of the functions will execute. Draw(1) will do the for loop and then return as it hits the end of the function (standard behaviour when you reach the end of a function even if theres no return statement). Then draw(2) will do the for loop and then return, etc. all the way up

  All parts of a function are recursive, theres no such thing as a non recursive part

  source
• Excrubulent@slrpnk.net ⁨10⁩ ⁨months⁩ ago

  The for loop doesn’t return, it’s just that when control flows to the end of the function, returning is the standard behaviour. It has nothing left to do, so control is returned to the calling code.

  The recursive portion is begun with draw(n - 1), but then you have a new for loop, because the same function has been called again. That’s what recursion is. Nothing in this function is non-recursive. It calls itself, so all of this code could be happening from the initial call, or within a recursive call. When draw(3) is called, you will get 3 for loops. You will actually get 4 draw calls, but the last one will be draw(0) which returns immediately.

  It’s confusing slightly because it works in reverse to what you’d expect. The operational part of the code - the part that does the drawing - only completes after the recursion is finished. That’s why it does draw(1) first, to maks the pyramid right way up.

  I don’t know that I’ve ever done recursion like this. It seems dsliberately fancy and somewhat confusing for a new learner.

  Imagine if you put the for loop before the recursive call. What would happen? You would draw three first, then decrease, so you would have an inverted pyramid. That would be easier to understand, but it would also not make a pyramid.

  source
• supernicepojo@lemmy.world ⁨10⁩ ⁨months⁩ ago

  This is all a really great example of how The Stack works. As the loop recurses it continually adds to the program stack in memory and then plays the next “item” in the stack. There is a specific limit to recursion as well based on this principle.

  source