Timeline for answer to Why a static main method in Java and C#, rather than a constructor? by oblitum
Current License: CC BY-SA 3.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 20, 2012 at 15:55 | comment | added | gbjbaanb | I'd say the problem was not having first-class functions. Sticking the main() inside an object (that isn't instantiated before the main gets called) is a bit of an anti-pattern. Maybe they should have an "application" object that gets constructed and runs its non-static main() method, then you can put startup initialisation in the constructor, and it would feel a lot better than having static methods, though a simple top-=level main() fn would be good too. Static main is a bit of a kludge all in all. | |
| Jul 11, 2012 at 21:22 | history | edited | oblitum | CC BY-SA 3.0 |
added 5 characters in body
|
| Jul 11, 2012 at 21:07 | history | edited | oblitum | CC BY-SA 3.0 |
added 719 characters in body
|
| Jul 11, 2012 at 20:08 | history | edited | oblitum | CC BY-SA 3.0 |
added 132 characters in body
|
| Jul 11, 2012 at 19:44 | history | answered | oblitum | CC BY-SA 3.0 |