Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #65152 > unrolled thread
| Started by | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| First post | 2014-02-01 10:59 +1100 |
| Last post | 2014-02-01 10:59 +1100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: __init__ is the initialiser Ben Finney <ben+python@benfinney.id.au> - 2014-02-01 10:59 +1100
| From | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| Date | 2014-02-01 10:59 +1100 |
| Subject | Re: __init__ is the initialiser |
| Message-ID | <mailman.6232.1391212793.18130.python-list@python.org> |
Ned Batchelder <ned@nedbatchelder.com> writes: > On 1/31/14 6:05 PM, Ben Finney wrote: > > Here we disagree. I think the meaning “… and that returns the new > > instance” is entailed in the meaning of “constructor”. > > […] > > You say these terms already have meanings, and that constructor means > a function that returns the new instance. Then your word "constructor" > isn't the same as C++'s word "constructor"? Those don't return the > instance. Neither do Java constructors. In terms of the code > developers actually write in __init__, it looks an awful lot like a > C++ or Java constructor, and serves precisely the same purpose. These are good points, thanks for raising them. -- \ Lucifer: “Just sign the Contract, sir, and the Piano is yours.” | `\ Ray: “Sheesh! This is long! Mind if I sign it now and read it | _o__) later?” —http://www.achewood.com/ | Ben Finney
Back to top | Article view | comp.lang.python
csiph-web