Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #29039
| From | Ulrich Eckhardt <ulrich.eckhardt@dominolaser.com> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: main and dependent objects |
| Date | 2012-09-13 17:05 +0200 |
| Message-ID | <da99i9-jpt.ln1@satorlaser.homedns.org> (permalink) |
| References | <mailman.601.1347540680.27098.python-list@python.org> |
Am 13.09.2012 14:51, schrieb andrea crotti: > I am in a situation where I have a class Obj which contains many > attributes, and also contains logically another object of class > Dependent. > > This dependent_object, however, also needs to access many fields of the > original class, so at the moment we did something like this: [...] > I could of course passing all the arguments needed to the constructor of > Dependent, but it's a bit tedious.. Jean-Michel already asked a good question, i.e. whether those two classes should be separate at all. I'll ask a similar question: Can't the shared data be put into a third, separate class? That way passing all the needed arguments wouldn't be tedious any more. Also, it makes clear that both outer and inner class depend on common data, but that the inner class doesn't depend on the outer beyond that. Now, just to get at least something Python-specific into this, you could override the __getitem__ of the inner class and transparently look up the item in the outer class if the inner class doesn't have it. Uli
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
main and dependent objects andrea crotti <andrea.crotti.0@gmail.com> - 2012-09-13 13:51 +0100 Re: main and dependent objects Ulrich Eckhardt <ulrich.eckhardt@dominolaser.com> - 2012-09-13 17:05 +0200 Re: main and dependent objects alex23 <wuwei23@gmail.com> - 2012-09-13 19:05 -0700
csiph-web