in reply to Re: Logging run-time warnings from an embedded perl interpreter
in thread [RESOLVED*] Logging run-time warnings from an embedded perl interpreter
I just put strict and warnings into my code and now I remember why I don't do that with this software :)
When a user-specified block of code is evaluated, some variables are already created in it's scope. If you use those variables in your code and then enable strict and warnings the application won't save your code to run later.
I side-stepped the warnings with the ever-so-icky my $pre_set_var if 0; construct (which I learned about here just a few weeks ago!)
Anyhow, I've enabled strict and warnings and even diagnostics, but I've still no clue how to get the stuff those spit out on STDERR into a log file for an embedded interpreter!
When a user-specified block of code is evaluated, some variables are already created in it's scope. If you use those variables in your code and then enable strict and warnings the application won't save your code to run later.
I side-stepped the warnings with the ever-so-icky my $pre_set_var if 0; construct (which I learned about here just a few weeks ago!)
Anyhow, I've enabled strict and warnings and even diagnostics, but I've still no clue how to get the stuff those spit out on STDERR into a log file for an embedded interpreter!
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^3: Logging run-time warnings from an embedded perl interpreter
by Corion (Patriarch) on Nov 19, 2007 at 19:19 UTC | |
by Hercynium (Hermit) on Nov 19, 2007 at 20:16 UTC | |
Re^3: Logging run-time warnings from an embedded perl interpreter
by Anonymous Monk on Nov 19, 2007 at 18:46 UTC | |
by Hercynium (Hermit) on Nov 19, 2007 at 19:21 UTC | |
Re^3: Logging run-time warnings from an embedded perl interpreter
by jbert (Priest) on Nov 20, 2007 at 08:58 UTC | |
by Hercynium (Hermit) on Nov 25, 2007 at 15:50 UTC |
In Section
Seekers of Perl Wisdom