Timeline for answer to Why a static main method in Java and C#, rather than a constructor? by Yam Marcovic
Current License: CC BY-SA 3.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 21, 2012 at 21:47 | comment | added | Yam Marcovic | @KonradRudolph True, but the initialization of a program is only one part of the initialization of a process, and doesn't legitimize a program constructor. | |
| Jul 20, 2012 at 16:42 | comment | added | Konrad Rudolph | Like I said below someguy’s answer, this isn’t relevant. What’s relevant is logical consistency. Logically, processes are represented as objects by the launcher (OS, JVM, whatever) and are initialised. | |
| Jul 20, 2012 at 16:30 | comment | added | Yam Marcovic | A process is a running program, and you can only start a process once via one entry point. Threads have their own entry points but are still within the same process. | |
| Jul 20, 2012 at 16:27 | comment | added | Konrad Rudolph |
I think you are wrong there. It is possible to have more than one process, hence more than one object. Incidentally, this is entirely equivalent to instantiating Runnable objects to have multiple threads.
|
|
| Jul 20, 2012 at 16:23 | history | answered | Yam Marcovic | CC BY-SA 3.0 |