On Sat, Sep 18, 2004 at 09:35:47PM -0700, Glenn Linderman wrote:
I have a pp question. When I build a standalone .exe on a machine that has all the needed modules, they all get bundled correctly, and everything works. But if a needed module is not installed on the machine when pp is run to create the .exe, it seems that the module is silently omitted from the .exe. And then the .exe fails when executed, reporting the missing module at that point in time.
Is there any way to convince pp to produce an error or warning diagnostic in such cases?
Yes: "pp -c" will report "use Module ()" errors, and "pp -x" will also do that, as well as reporting "require Module" errors.
Thanks. And here I thought I could read the documentation! I guess I skipped those because (1) they look like they do "more than the usual work" to analyze dependencies (2) when all the Modules actually exist, they do get included with the "usual work" (3) they don't mention a thing about giving extra warnings.
Is there a way to get extra warnings, without doing extra dependency checking? I'd guess not, or you'd have mentioned it. But you see, I'm not interested in finding _additional_ run-time dependencies, just in getting a report of the _usual_ ones that aren't found. Is this a missing capability?
Speaking of reading documentation, see my next email...
-- Glenn -- http://nevcal.com/ =========================== The best part about procrastination is that you are never bored, because you have all kinds of things that you should be doing.
