Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > Python > Does RETURN_VALUE always result in an empty stack?

Thread Tools

Does RETURN_VALUE always result in an empty stack?

Posts: n/a
I'm developing PyMite and would like to know a little detail about
Python 2.5's design. Is it true that when the RETURN_VALUE executes
and pops its argument, that at that point the stack should *always* be
empty? I mean just the argument stack for that execution frame. I
want to use this knowledge to test if PyMite is working properly.



Reply With Quote

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Is the result of valid dynamic cast always equal to the result ofcorrespondent static cast? Pavel C++ 7 09-18-2010 11:35 PM
simulation result is correct but synthesis result is not correct J.Ram VHDL 7 12-03-2008 01:26 PM
Help with SP - what exactly is RETURN_VALUE? D. Shane Fowlkes ASP .Net 9 03-14-2006 08:41 AM
1. Ruby result: 101 seconds , 2. Java result:9.8 seconds, 3. Perl result:62 seconds Michael Tan Ruby 32 07-21-2005 03:23 PM
Passing a DataReader between methods and getting RETURN_VALUE Martin Raychev ASP .Net 2 04-22-2004 09:23 PM