Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #13061
| References | (1 earlier) <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> <pan.2011.09.10.10.11.37.104000@nowhere.com> |
|---|---|
| Date | 2011-09-10 20:29 +1000 |
| Subject | Re: How to structure packages |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.931.1315650599.27778.python-list@python.org> (permalink) |
On Sat, Sep 10, 2011 at 8:11 PM, Nobody <nobody@nowhere.com> wrote: > 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. One class per object file isn't a problem - you can always .jar your classes if the proliferation of small files bothers you, and then it's just a different way of indexing the mound of code. One class per source file complicates the human's view in order to simplify the tools'. Not sure that's really worthwhile. > I never saw it as a problem, given that Java is fundamentally class-based: > there are no global variables or functions, only classes. Yeah... of course you can easily simulate globals with static members in a dedicated class, but it's slower. THIS, though, is where Java's security model comes in - you can assign security X to Globals1.class and security Y to Globals2.class, rather than trying to juggle security issues in a monolithic "globals" namespace. IMHO it's not worth the hassle, though. I'd rather just have globals. ChrisA
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