Hi David,
Your proposal is too vague to be useful. In Python I would not feel
that any compiler-enforced restrictions are going to be too restrictive,
and so I believe that your approach is not viable, but I cannot give you
many concrete examples of why before you come up with a more concrete
Armin Rigo wrote:
Hi David,
Your proposal is too vague to be useful. In Python I would not feel
that any compiler-enforced restrictions are going to be too restrictive,
and so I believe that your approach is not viable, but I cannot give you
many concrete examples of why before you come up
David Hopwood wrote:
The intention was not to require the restrictions to be compiler-enforced;
only to *allow* them to be compiler-enforced.
Code like this, for example:
def someMethod(self, x):
if self == x:
if self is x:, I meant.
foo(x._internal)
should not
David Hopwood wrote:
Inheritance should be defined as though the code of inherited methods and
attributes were copied into the subclass (with global accesses updated to
point to the original module).
You'll have to propose an implementation strategy for that
which works without actually
Greg Ewing wrote:
David Hopwood wrote:
Inheritance should be defined as though the code of inherited methods and
attributes were copied into the subclass (with global accesses updated to
point to the original module).
You'll have to propose an implementation strategy for that
which works
Richard Jones wrote:
On 27/07/2006, at 12:19 PM, David Hopwood wrote:
A restricted interpreter refuses access to any object attribute or
method with a name beginning with '_' (by throwing a new exception type
'InternalAccessException'), unless the access is from a method and its
[This message is cc:d to the e-lang list, but please take any replies to
[EMAIL PROTECTED]
Brett Cannon wrote:
On 7/19/06, Ka-Ping Yee [EMAIL PROTECTED] wrote:
OMG!!! Is all i can say at the moment. Very excited.
This is very encouraging. Thanks to ?!ng, Michael Chermside and others for
