Re^2: XS: use module into package

Replies are listed 'Best First'.
Re^3: XS: use module into package by ikegami (Patriarch) on Jun 13, 2011 at 18:27 UTC
I don't think so, but it's moot. The reason you had to use `eval` in code doesn't go away by loading the module using a different interface. You can't go and change the package the parent Perl code was compiled into.	[reply] [d/l]
Re^4: XS: use module into package by Anonymous Monk on Jun 13, 2011 at 18:54 UTC
But the code the eval executes is being parsed into a sequence of API calls that finally end up changing the caller package by using a module into it. I'm looking for these API functions. Except that maybe these are not "API" calls, but really internal stuff not meant for the general public.	[reply]
Re^5: XS: use module into package by ikegami (Patriarch) on Jun 13, 2011 at 19:13 UTC
You can't go and change the package the parent Perl code was compiled into. You have to create new code and have it executed by Perl. Perl code gets compiled into ops, not API calls. `package` itself doesn't even result in an op because it's compiler directive. It changes the package Perl code gets compiled into.	[reply] [d/l]
Re^6: XS: use module into package by Anonymous Monk on Jun 13, 2011 at 19:55 UTC
Re^7: XS: use module into package by ikegami (Patriarch) on Jun 13, 2011 at 20:56 UTC
Some notes below your chosen depth have not been shown here
Re^7: XS: use module into package by ikegami (Patriarch) on Jun 13, 2011 at 20:36 UTC