replying a couple of days late due to heavy weather conditions here ...
thanks to all those who replied, guys.
I should clarify that I did understand from the beginning, what the intention of his code was, for parsing and running that while statement. I am a dev myself. I mean, I did know that the purpose of that code part was to scan from the "while" line to the "end" line, executing the statements along the way, and then scan back up to the "while", and again execute the statements until the "end", and so on, as long as the while condition was true. and the RPN part was clear to me too, no issues there.
I mean, as somebody else commented, he says all that himself in the talk.
what I did not quite understand was some of the exact implementation details of that part. I think there were a couple of reasons for this. one, I may have spent too little time reading it, and two, as someone else again said, he jumps back and forth in the video, between writing bits of code and testing them, which makes it difficult to get a holistic view of the code at one time on the screen.
anyway I will go through it again, to make sense of the implementation details.
thanks to all those who replied, guys.
I should clarify that I did understand from the beginning, what the intention of his code was, for parsing and running that while statement. I am a dev myself. I mean, I did know that the purpose of that code part was to scan from the "while" line to the "end" line, executing the statements along the way, and then scan back up to the "while", and again execute the statements until the "end", and so on, as long as the while condition was true. and the RPN part was clear to me too, no issues there.
I mean, as somebody else commented, he says all that himself in the talk.
what I did not quite understand was some of the exact implementation details of that part. I think there were a couple of reasons for this. one, I may have spent too little time reading it, and two, as someone else again said, he jumps back and forth in the video, between writing bits of code and testing them, which makes it difficult to get a holistic view of the code at one time on the screen.
anyway I will go through it again, to make sense of the implementation details.