![[The AI Show Episode 149]: Google I/O, Claude 4, White Collar Jobs Automated in 5 Years, Jony Ive Joins OpenAI, and AI’s Impact on the Environment](https://www.marketingaiinstitute.com/hubfs/ep%20149%20cover.png)
_Illia_Uriadnikov_Alamy.jpg?width=1280&auto=webp&quality=80&disable=upscale#)
![PSA: Spotify facing widespread outage [U: Fixed]](https://i0.wp.com/9to5mac.com/wp-content/uploads/sites/6/2023/06/spotify-logo-2.jpg?resize=1200%2C628&quality=82&strip=all&ssl=1){kind=logo}
![Apple Turned Down Musk's $5B Starlink Deal — Now the Consequences Are Mounting [Report]](https://www.iclarified.com/images/news/97432/97432/97432-640.jpg)
![WhatsApp Finally Launches iPad App [Download]](https://www.iclarified.com/images/news/97435/97435/97435-640.jpg)
![T-Mobile, Verizon and AT&T under fire for lack of transparency on surveillance [UPDATED]](https://m-cdn.phonearena.com/images/article/170786-two/T-Mobile-Verizon-and-AT-T-under-fire-for-lack-of-transparency-on-surveillance-UPDATED.jpg?#)
In c/c++, are block-scope variables stacked only if the block is executed?
Suppose this: void func() { ... if( blah ) { int x; } ... } Is the space for x reserved on the stack immediately when func is entered, or only if the block is actually executed? Or is it the compiler's choice? Do C and C++ behave the same about this?
Suppose this:
void func()
{
...
if( blah )
{
int x;
}
...
}
Is the space for x reserved on the stack immediately when func is entered, or only if the block is actually executed?
Or is it the compiler's choice?
Do C and C++ behave the same about this?
