Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #6720 > unrolled thread
| Started by | Wolfgang Rohdewald <wolfgang@rohdewald.de> |
|---|---|
| First post | 2011-05-31 10:37 +0200 |
| Last post | 2011-05-31 10:37 +0200 |
| 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: scope of function parameters (take two) Wolfgang Rohdewald <wolfgang@rohdewald.de> - 2011-05-31 10:37 +0200
| From | Wolfgang Rohdewald <wolfgang@rohdewald.de> |
|---|---|
| Date | 2011-05-31 10:37 +0200 |
| Subject | Re: scope of function parameters (take two) |
| Message-ID | <mailman.2312.1306831063.9059.python-list@python.org> |
On Dienstag 31 Mai 2011, Henry Olders wrote: > You're partially right - what I want is a function that is > free of side effects back through the parameters passed in > the function call. I don't know any object oriented language where it is not possible to change objects passed in as parameters. It is up to the passed object (a list in your case) to allow or disallow manipulations no matter how they are invocated, and the object is the same in the calling code and in the called function. -- Wolfgang
Back to top | Article view | comp.lang.python
csiph-web