Timeline for Why the static data members have to be defined outside the class separately in C++ (unlike Java)?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 20, 2013 at 10:18 | comment | added | ixache | @Giorgio: the reference to Java may not be welcome, but I think that Emilio's answer is mostly right by getting to the gist of the issue, namely the object file/linker phase after separate compilation. | |
| S Sep 20, 2013 at 10:05 | history | suggested | CommunityBot | CC BY-SA 3.0 |
Correcting a few typos and some grammar
|
| Sep 20, 2013 at 9:59 | review | Suggested edits | |||
| S Sep 20, 2013 at 10:05 | |||||
| Nov 18, 2012 at 11:41 | comment | added | Giorgio | The difference between Java and C++ with respect to global symbols is not connected with Java having a virtual machine, but rather with the C++ compilation model. In this respect, I would not put Pascal and C++ in the same category. Rather I would group C and C++ together as "languages in which the imported declarations are included and compiled together with the main source file" as opposed to Java and Pascal (and maybe OCaml, Scala, Ada, etc) as "languages in which the imported declarations are looked up by the compiler in pre-compiled files containing information about exported symbols". | |
| Apr 21, 2012 at 7:10 | history | answered | Emilio Garavaglia | CC BY-SA 3.0 |