how does .net managed memory hoop value forms inside objects?


public category myclass
{
open int age;
open int id;
}

public vacant mymethod()
{
myclass m = new myclass();
int newid;
}


to understanding, following true:




  1. the anxiety m lives smoke-stack goes out range mymethod() exits.

  2. the value form newid lives smoke-stack goes out range mymethod() exits.

  3. the vigilant combined new user lives store becomes reclaimable gc mymethod() exits, presumption anxiety vigilant exists.



here question:




  1. do value forms within objects live smoke-stack heap?

  2. is boxing/unboxing value forms an vigilant concern?

  3. are there any detailed, nonetheless understandable, resources topic?



logically, i'd cruise value forms inside classes heap, nonetheless i'm certain have boxed there.



edit:



suggested reading topic:




  1. clr around c# jeffrey richter

  2. essential .net enclose box



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members