Why functional Python matters
Jp Calderone
exarkun at intarweb.us
Tue Apr 15 20:35:24 EDT 2003
On Tue, Apr 15, 2003 at 11:17:26PM -0000, Dave Benjamin wrote:
> In article <yfs7k9vcu2p.fsf at black132.ex.ac.uk>, Alexander Schmolck wrote:
> [snip]
>
> >> keyword-argument trick wasn't really that bad, once you got used to it. In
> >> any case, with dynamic scoping, this problem has completely disappeared.
> > ^^^^^^^^^^^^^^^
> > not quite.
>
> Am I using the wrong terminology here? I'm specifically talking about the
> named-argument hack to get around Python's previous lack of nested scopes.
> This specific problem, as far as I know, is gone now. Am I missing something?
>
I think you meant "partial lexical scoping" ;) Dynamic scoping is what
Python used to do. Since it isn't quite lexical scoping, it's best to just
stick with the term "nested scopes".
> [snip]
Jp
--
#!/bin/bash
( LIST=(~/.sigs/*.sig)
cat ${LIST[$(($RANDOM % ${#LIST[*]}))]}
echo -- $'\n' `uptime | sed -e 's/.*m//'` ) > ~/.signature
--
up 26 days, 21:02, 4 users, load average: 0.25, 0.31, 0.63
More information about the Python-list
mailing list