Re: What about letting x.( ... ? ... ) be equivalent to ( ... x ... )

2005-10-09 Thread Daniel Delay
Diez B. Roggisch a écrit : > Apart from that, I don't think your proposal does any good - it is ugly > (or at least not less ugly than the things you want to fix) and confuses > the reader because of the colliding use of . for attribute access. There is no ambiguity ( in one case "." is followe

Re: What about letting x.( ... ? ... ) be equivalent to ( ... x ... )

2005-10-09 Thread daniel delay
to your reply. I tried with two different providers to get the messages, but with the same result. Is it possible that this msg could have been throwned away by moderators of this list ?? But in this case, you wouldn't have been able to read it... Daniel delay -- http://mail.python.org/mailman/listinfo/python-list

Re: What about letting x.( ... ? ... ) be equivalent to ( ... x ... )

2005-10-09 Thread daniel delay
Fredrik Lundh a écrit : > [EMAIL PROTECTED] wrote: > > >>These 3 intermediate variables used to improve readability >>can introduce bugs : you have to check that b, c and d are >>not used anywhere else in the code. > > > if you have a fear of introducing new local variables, you have problems >