Did you catch the last line of my post:
No I have problems to parse the phrase structure, sorry.
No, I'm sorry! Thank you for your patience. Anyway, ignoring that -- I tried
to "re-explain it" -- why using Exporter would be a problem. I probably could do something similar with the "export_to_level" ... but why? It seems like overkill to pull in Exporter to do what took 3-4 lines of code in my module -- just to get "away" from using "use vars".
On calling vars->import(List), do you mean in the program that's using the module? Where would var->import import things from? I.e. do you mean I'd do something like:
use Cmds qw(sudo dd);
vars->import(Sudo Dd);
It seems cleaner to only specify the external cmd list once, but I'm not sure this is what you meant.
As for setting the stash -- probably could but that'd involve getting more into the internals of perl and I'd prefer to not do that, since the perl internals could easily change in a new release and then I'd have to fix my usage of it. More work! ARG! :-)
Why would I want to steer away from the eval? This is code that is usually only executed once
at BEGIN time.
While I may not want to go back and change this module, I probably do want to go change some other modules I care about more, I'm still not clear why I'd prefer to get deeper into perl internals to get away from a "generic" eval? Most of my modules work back to 5.8 and some back to 5.6. I usually try to spend sometime to use less advanced methods so I can be compatible with older perls. Not always successful, but I still try.
-linda
|