Nick Ing-Simmons wrote: > Ah, oops sorry I missed the PPCODE vs CODE issue. > (The machine-level programmer in me distrusts moving the stack back before > one is finished with it so for that reason I seldom use PPCODE.) I'm pushing variably sized lists onto the stack, for example when called in a scalar context the routine returns a single value, and a list when called in a list context (or an empty list on error). According to perlxs if you are going to do that sort of thing you need to use PPCODE instead of CODE: Isn't that correct? Alan Burlison
- Manipulating the perl stack from within a non-XSUB functi... Alan Burlison
- Re: Manipulating the perl stack from within a non-XS... Alan Burlison
- Re: Manipulating the perl stack from within a no... Stephen Zander
- Re: Manipulating the perl stack from within ... Alan Burlison
- Re: Manipulating the perl stack from within a non-XS... Nick Ing-Simmons
- Re: Manipulating the perl stack from within a no... Alan Burlison
- Re: Manipulating the perl stack from within a no... Alan Burlison
- Re: Manipulating the perl stack from within ... Nick Ing-Simmons
- Re: Manipulating the perl stack from wit... Alan Burlison
- Re: Manipulating the perl stack fro... Nick Ing-Simmons
