GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [Python-Dev] new draft of PEP 227
  • [Python-Dev] new draft of PEP 227
  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] new draft of PEP 227

[Python-Dev] new draft of PEP 227

Greg Ewing [email protected]
Fri, 15 Dec 2000 12:58:24 +1300 (NZDT)

  • Previous message: [Python-Dev] new draft of PEP 227
  • Next message: [Python-Dev] new draft of PEP 227
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Paul Prescod <[email protected]>:

> We could say that a local can only shadow a global 
> if the local is formally declared.

How do you intend to enforce that? Seems like it would
require a test on every assignment to a local, to make
sure nobody has snuck in a new global since the function
was compiled.

> Actually, one could argue that there is no good reason to 
> even *allow* the shadowing of globals.

If shadowing were completely disallowed, it would make it
impossible to write a completely self-contained function
whose source could be moved from one environment to another
without danger of it breaking. I wouldn't like the language
to have a characteristic like that.

Greg Ewing, Computer Science Dept, +--------------------------------------+
University of Canterbury,	   | A citizen of NewZealandCorp, a	  |
Christchurch, New Zealand	   | wholly-owned subsidiary of USA Inc.  |
[email protected]	   +--------------------------------------+



  • Previous message: [Python-Dev] new draft of PEP 227
  • Next message: [Python-Dev] new draft of PEP 227
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.