On 4/26/06, Edward Elliott <[EMAIL PROTECTED]> wrote:
> Sion Arrowsmith wrote:
> > Absolutely. I've written quite a lot of code (which I wasn't expecting
> > anyone else to maintain) using 'I' for the same reasons. Plus, it's
> > even shorter in terms of characters (if not keystrokes), stands out
>
Sion Arrowsmith wrote:
> Absolutely. I've written quite a lot of code (which I wasn't expecting
> anyone else to maintain) using 'I' for the same reasons. Plus, it's
> even shorter in terms of characters (if not keystrokes), stands out
> reasonably well, and for how I read it makes for better Engli
Edward Elliott <[EMAIL PROTECTED]> wrote:
>If compactness is all you want, shorten self to s. Personally I like 'me'
>as it's both shorter and more vernacular:
>
>def do_GET (me):
>me.send_response (200, "ok")
Absolutely. I've written quite a lot of code (which I wasn't expecting
anyone else
[EMAIL PROTECTED] wrote:
> It's less explicit than self. but it's shorter, this improves typing,
> and allows to produce more compact code:
>
> return "".join(["Graph(", repr($o), ", ", repr($nodeData), ")"])
>
> Instead of:
>
> return "".join(["Graph(", repr(self.o), ", ", repr(self.nodeData),
[EMAIL PROTECTED] enlightened us with:
> Some people like and use them often (like those ones coming from
> Pascal-like languages, etc), some other people (like those coming
> from C-like languages like Java) use them rarely and like classes
> more. Python can choose to have just one way to solve
Stelios Xanthakis:
>in my opinion nested functions are not so important and I wouldn't spend any
>time to improve them. Usually you can do anything with classes<
Some people like and use them often (like those ones coming from
Pascal-like languages, etc), some other people (like those coming fro
Hi,
[EMAIL PROTECTED] wrote:
> but maybe instead of the global.name something to refer to the upper
> namespace (that can be the global one or the namespace of the function
> that contains this one) can be more general:
> upper.x = 1
> upper.upper.x = 1
>
Well, people have been trying to come u
> "Stelios" == Stelios Xanthakis <[EMAIL PROTECTED]> writes:
Stelios> It had to happen :) http://pyvm32.infogami.com/EPL
Stelios> Seriously, this is not so much about the whitespace as
Stelios> for the new features, which might interest people who are
Stelios> thinking about n
On 4/15/06, Stelios Xanthakis <[EMAIL PROTECTED]> wrote:
> It had to happen :)
Did it?
> http://pyvm32.infogami.com/EPL
>
> Seriously, this is not so much about the whitespace as for the
> new features, which might interest people who are thinking about
> new features. More specifically,
Stelios Xanthakis wrote:
> It had to happen :)
>
> http://pyvm32.infogami.com/EPL
>
> Seriously, this is not so much about the whitespace as for the
> new features, which might interest people who are thinking about
> new features. More specifically, "methods" and the "$" operator
> are reall
This seems nice:
global.x = 1
is the same as
global x
x = 1
but maybe instead of the global.name something to refer to the upper
namespace (that can be the global one or the namespace of the function
that contains this one) can be more general:
upper.x = 1
upper.upper.x = 1
I think that making se
It had to happen :)
http://pyvm32.infogami.com/EPL
Seriously, this is not so much about the whitespace as for the
new features, which might interest people who are thinking about
new features. More specifically, "methods" and the "$" operator
are really great and seem to solve the problem
12 matches
Mail list logo
