Timeline for How does the ref keyword work (in terms of memory)
Current License: CC BY-SA 4.0
11 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 26, 2019 at 9:26 | history | edited | Tamas Hegedus | CC BY-SA 4.0 |
added 2 characters in body
|
Jan 3, 2016 at 1:01 | history | edited | Tamas Hegedus | CC BY-SA 3.0 |
deleted 7 characters in body
|
Jan 2, 2016 at 22:13 | comment | added | Jon Hanna | Yep. That nit picked, +1. | |
Jan 2, 2016 at 20:00 | comment | added | Tamas Hegedus | @JonHanna Please read forward my answer. I edited the first sentence so it is more clear which case i am referring to | |
Jan 2, 2016 at 19:59 | history | edited | Tamas Hegedus | CC BY-SA 3.0 |
added 15 characters in body
|
Jan 2, 2016 at 19:50 | comment | added | Jon Hanna |
"the referenced int will be put on the stack" is not true, your example puts it on the stack with var i = 7; but ref would also work if it referenced a field of an object on the heap, or an element of an array.
|
|
Jan 2, 2016 at 19:45 | history | edited | Tamas Hegedus | CC BY-SA 3.0 |
added 26 characters in body
|
Jan 2, 2016 at 19:00 | vote | accept | Foo | ||
Jan 2, 2016 at 18:55 | history | edited | Tamas Hegedus | CC BY-SA 3.0 |
deleted 177 characters in body
|
Jan 2, 2016 at 18:50 | history | edited | Tamas Hegedus | CC BY-SA 3.0 |
Added passing members by reference
|
Jan 2, 2016 at 18:36 | history | answered | Tamas Hegedus | CC BY-SA 3.0 |