Quoting Bert Wesarg <[EMAIL PROTECTED]>: > Hi Tony, > > I know we should concentrate on the next release, but whatever. > > In your patchset, you add the localsymlist into the current stack > frame. The only use for this seems to be debugging. May I propose to > use this list to store the values of these symbols instead of the > pushed values onto the stack? > > A deeper look, and I have the feeling, that in the current cvs code, > the local sym push to the stack is also not neccesery. > > So, maybe you have an argument why the local syms are on the stack.
Yes: I push this to get the symbol names only. You must NOT use the symlist for actual value storage: there is only one for each function. Each value in the symlist is the numeric position relative to the frame pointer of the function where the actual value in a call's execution is stored. In other words, the symlist is a lookup table for the stack frame. Why would you not want to push the symbols' values onto the stack? As for storing the list for debug lookup, you do have a case. But I get debugging ;) Tony -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
