Loading video...

Video Failed to Load

Go Home

Jerry Cain explains how the stack manages function calls. Source: Professor Jerry Cain, Programming Paradigms, Stanford (CS107):

452,683 views • 1 year ago •via X (Twitter)

11 Comments

Vladimir Kameñar's profile picture
Vladimir Kameñar1 year ago

That's a complex and confusing explanation for a simple concept.

Rainmaker's profile picture
Rainmaker1 year ago

Decode the labor market! Learn how to track jobless claims using FRED and Python in my latest free Substack post. 📈 A must-read for data enthusiasts & economists. Dive into how data insights can shape your understanding of the economy.

asciinish's profile picture
asciinish1 year ago

I think we should collaborate and make a complete archive of lectures that lead to a certain path, since, you are into these too

Lee Revell's profile picture
Lee Revell1 year ago

You should post this one at 1x speed and edit out less.

asciinish's profile picture
asciinish1 year ago

Jerry cain, the kingmaker of core programming and dynamic processing, just ignore his silly mistakes 😅

Tristan🎗's profile picture
Tristan🎗1 year ago

Does the video speed normal? Looks like *2 for me.

Cristiano Camacho 🗡️⚔'s profile picture
Cristiano Camacho 🗡️⚔1 year ago

Thank you so much for this group and these videos. As a C/ASM dev, I often think I'm alone, then I remember there are other people like me in this group :)

Marc Compere's profile picture
Marc Compere1 year ago

this one was beyond my current knowledge level 🤔👍

🐀's profile picture
🐀1 year ago

I wonder who is gonna notice the potential vuln.

Sudarahan Kakoty's profile picture
Sudarahan Kakoty1 year ago

My bad, I understood absolutely nothing

Lee Revell's profile picture
Lee Revell1 year ago

Yeah, I think his point is that with each function call the locals of the previous function go out of scope but can be accessed again upon return(). Obvious, or is he saying something else

Related Videos