Re: Are the CALL_FUNCTION_* opcodes ever used?

2006-09-22 Thread Fabiano Sidler
On Thursday 21 September 2006 22:36, Peter Otten wrote: > >>> def test(): > > ... func(*args) > ... func(**kw) > ... func(*args, **kw) Oh, I didn't know the possibility of using the *args and **kwargs semantics at function call. Thank you for revealing them to me! :) Now it is also obv

Re: Are the CALL_FUNCTION_* opcodes ever used?

2006-09-21 Thread Peter Otten
Fabiano Sidler wrote: > Studying python byte code I encountered an interesting issue: there is no > matter, which one of the following function calls I compile: > > 1: func('foo','bar',foo='bar') > 2: func('foobar') > 3: func(foo='bar') > > The compiler always uses the simple CALL_FUNCTION for a

Are the CALL_FUNCTION_* opcodes ever used?

2006-09-21 Thread Fabiano Sidler
Hi folks! Studying python byte code I encountered an interesting issue: there is no matter, which one of the following function calls I compile: 1: func('foo','bar',foo='bar') 2: func('foobar') 3: func(foo='bar') The compiler always uses the simple CALL_FUNCTION for all of the source examples ab