Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #13059
| From | Nobody <nobody@nowhere.com> |
|---|---|
| Subject | Re: How to structure packages |
| Date | 2011-09-10 11:11 +0100 |
| Message-Id | <pan.2011.09.10.10.11.37.104000@nowhere.com> |
| Newsgroups | comp.lang.python |
| References | <2a4f542c-a8c1-46c7-9899-a3fad0940cf6@x11g2000yqc.googlegroups.com> <mailman.842.1315416661.27778.python-list@python.org> <4e680c67$0$29980$c3e8da3$5496439d@news.astraweb.com> <pan.2011.09.09.00.45.41.959000@nowhere.com> <mailman.890.1315532266.27778.python-list@python.org> |
| Organization | Zen Internet |
On Fri, 09 Sep 2011 11:37:44 +1000, Chris Angelico wrote: >> The Java compiler also acts as a "make" program. If it doesn't find >> a .class file for a needed class, it will search for the corresponding >> .java file and compile that. So to compile a complex program, you only >> need to compile the top-level file (e.g. HelloWorld.java), and it will >> compile everything which is required. No Makefile is needed, as the >> relationship between classes, object files and source files is fixed. >> > > If that's the entire benefit, then I think this is a rather hefty > price to pay for the elimination of a makefile. It also eliminates the need for TAGS files, browser database (PDB) files, etc. Once you know the class name, all of the filenames follow from that. I suspect that the one-to-one correspondence between classes and .class files is mostly technical (e.g. Java's security model). The one-to-one correspondence between class files and source files could probably be relaxed, but at the expense of complicating the IDE and toolchain. I never saw it as a problem, given that Java is fundamentally class-based: there are no global variables or functions, only classes.
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to structure packages bclark76 <bclark76@gmail.com> - 2011-09-07 08:56 -0700
Re: How to structure packages John Gordon <gordon@panix.com> - 2011-09-07 16:11 +0000
Re: How to structure packages Rafael Durán Castañeda <rafadurancastaneda@gmail.com> - 2011-09-07 19:18 +0200
Re: How to structure packages Peter Otten <__peter__@web.de> - 2011-09-07 19:30 +0200
Re: How to structure packages Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2011-09-08 10:29 +1000
Re: How to structure packages Chris Angelico <rosuav@gmail.com> - 2011-09-08 12:39 +1000
Re: How to structure packages Dan Sommers <dan@tombstonezero.net> - 2011-09-08 09:51 +0000
Re: How to structure packages Jonathan Hartley <tartley@tartley.com> - 2011-09-08 03:22 -0700
Re: How to structure packages Nobody <nobody@nowhere.com> - 2011-09-09 01:45 +0100
Re: How to structure packages Chris Angelico <rosuav@gmail.com> - 2011-09-09 11:37 +1000
Re: How to structure packages Nobody <nobody@nowhere.com> - 2011-09-10 11:11 +0100
Re: How to structure packages Chris Angelico <rosuav@gmail.com> - 2011-09-10 20:29 +1000
Re: How to structure packages "Littlefield, Tyler" <tyler@tysdomain.com> - 2011-09-10 08:04 -0600
Re: How to structure packages Alec Taylor <alec.taylor6@gmail.com> - 2011-09-10 02:38 +1000
Re: How to structure packages rantingrick <rantingrick@gmail.com> - 2011-09-07 10:56 -0700
Re: How to structure packages "Littlefield, Tyler" <tyler@tysdomain.com> - 2011-09-07 12:11 -0600
Re: How to structure packages Westley Martínez <anikom15@gmail.com> - 2011-09-07 14:35 -0700
csiph-web