in reply to Re^3: perl interpreter must be named my_perl?
in thread perl interpreter must be named my_perl?
No, that's all wrong. The THX macros don't care about the name of the "top-level" variable.
aTHX should only be used in a function which either has pTHX in its parameter list or in which dTHX; is used. In a MULTIPLICITY build, aTHX will only access the parameter var named my_perl created by pTHX or the local var named my_perl created by dTHX. In other words, it only accesses the my_perl variable the THX macros create themselves.
In a non-MULTIPLICITY build, those macros are all undefined. They don't mention my_perl at all.
So either way, they don't care about the name of the name of the "top-level" variable.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^5: perl interpreter must be named my_perl?
by Anonymous Monk on Dec 01, 2023 at 05:33 UTC | |
by ikegami (Patriarch) on Dec 01, 2023 at 19:22 UTC | |
by bliako (Abbot) on Dec 01, 2023 at 08:05 UTC | |
by etj (Priest) on Jan 08, 2025 at 23:39 UTC |