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


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

Re: scope of function parameters (take two)

Started byHenry Olders <henry.olders@mcgill.ca>
First post2011-05-31 02:37 -0400
Last post2011-05-31 02:37 -0400
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) Henry Olders <henry.olders@mcgill.ca> - 2011-05-31 02:37 -0400

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

FromHenry Olders <henry.olders@mcgill.ca>
Date2011-05-31 02:37 -0400
SubjectRe: scope of function parameters (take two)
Message-ID<mailman.2303.1306823870.9059.python-list@python.org>
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. 

python seems to be undergoing changes all the time. List comprehensions were added in python 2.0, according to wikipedia. I like list comprehensions and use them all the time because they are powerful and concise.
> 
> did you read the link Steven gave you?
> http://mail.python.org/pipermail/tutor/2010-December/080505.html

Yes, I did, thanks.

Henry

[toc] | [standalone]


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


csiph-web