Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Gregory Ewing Newsgroups: comp.lang.python Subject: Re: Uniform Function Call Syntax (UFCS) Date: Sun, 08 Jun 2014 13:27:42 +1200 Lines: 11 Message-ID: References: <8b96ae27-20fa-4df9-807e-c806fed983c0@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 9kDPgIBBnllQPpEdM7ro3ArouE6AGUvZiuQx6WAZ+BpGyJlzj4 Cancel-Lock: sha1:6IVB/LL06Sg/gyT0kPd0o+GSjgg= User-Agent: Mozilla Thunderbird 1.0.5 (Macintosh/20050711) X-Accept-Language: en-us, en In-Reply-To: Xref: csiph.com comp.lang.python:72947 Ian Kelly wrote: > It's a nice feature in a statically typed language, but I'm not sure > how well it would work in a language as dynamic as Python. Also it doesn't sit well with Python's "one obvious way to do it" guideline, because it means there are *two* equally obvious ways to call a function. -- Greg