Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #6712 > unrolled thread

Re: scope of function parameters (take two)

Started byChris Rebert <clp2@rebertia.com>
First post2011-05-30 23:54 -0700
Last post2011-05-30 23:54 -0700
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.


Contents

  Re: scope of function parameters (take two) Chris Rebert <clp2@rebertia.com> - 2011-05-30 23:54 -0700

#6712 — Re: scope of function parameters (take two)

FromChris Rebert <clp2@rebertia.com>
Date2011-05-30 23:54 -0700
SubjectRe: scope of function parameters (take two)
Message-ID<mailman.2304.1306824852.9059.python-list@python.org>
On Mon, May 30, 2011 at 11:37 PM, Henry Olders <henry.olders@mcgill.ca> wrote:
> On 2011-05-31, at 1:13 , Wolfgang Rohdewald wrote:
>>
>> what you really seem to want is that a function by default
>> cannot have any side effects (you have a side effect if a
>> function changes things outside of its local scope). But
>> that would be a very different language than python
>
> 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. Side effects via globals or print statements is fine by me.

So, you have no problem with *global* side effects, but side effects
with a /more constrained/ scope bother you?
That's kinda odd, IMO.

Cheers,
Chris

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web