Timeline for Why Java Collections class is not final?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 18, 2016 at 18:11 | history | edited | Servy | CC BY-SA 3.0 |
deleted 17 characters in body
|
| Oct 18, 2016 at 18:06 | comment | added | SusanW | @SebastianRedl Yep exactly. Under the covers, C++ static data is just like C static data, and "static" acquired the association of representing class-scoped members. | |
| Sep 28, 2016 at 20:34 | comment | added | Sebastian Redl | I interpret "hence the name" as "that's that reason for the name". Anyway, the name derives from C's static local variables (same as in Java), which have static existence (as opposed to the dynamic existence of normal variables). The keyword was reused by C++ to denote member variables that are not bound to one instance, and then by Java for the same purpose. | |
| Sep 28, 2016 at 19:20 | comment | added | Erik Eidt | @SebastianRedl, Servy is not claiming anything about the actual reason for the name. However, feel free to enlighten us, since you've broached the subject: what is the actual reason for the name? | |
| Sep 28, 2016 at 17:05 | comment | added | Sebastian Redl | That's a nice way to remember it, but it is not the actual reason for the name. | |
| Sep 28, 2016 at 16:46 | history | answered | Servy | CC BY-SA 3.0 |