On 9/18/05, Greg Ewing <[EMAIL PROTECTED]> wrote: > François Pinard wrote: > > > The only practical reason to like this feature is sparing the need of > > finding an otherwise useless name for the formal argument. > > If the argument represents a coherent enough concept > to be passed in as a tuple in the first place, it > should be possible to find a meaningful name for it. > Otherwise the elements should probably be passed in > as separate arguments. > > > Yet, if I was given the choice between nested tuple function arguments, > > and faster argument processing, the latter would win instantly. > > I believe that exactly the same bytecode results either > way, so there's no speed advantage or penalty. >
Yep, the bytecode will be the same sans the compiler-created name for the tuple . -Brett _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
