Ariel Scolnicov wrote:
> However, I'd much rather *not* have such a menu, and certainly not
> *on* by default. A menu is not particularly useful to me, nor is
> running the file through `less'; I use XEmacs for examining files (and
> I'm sure others have their own preferences). Putting all the files in
> blib_I/errors/ (and adding a reference to that directory in the error
> message) is certainly good enough for me to figure out the problem.
>
> If we *must* have this menu, I still don't want it on by default.
> Production code should *never* do this sort of thing. If a user tries
> to run some Perl with Inline'd code and fails due to being over disk
> quota, I *don't* want her presented with a menu of files to inspect.
> I want an honest error message, which can be examined and emailed me
> if necessary.
>
> At the very very very very very least, any type of interaction should
> first check the environment variable PL_INLINE_ERROR_INTERACTIVE (I'm
> not particular about the name) is set.
So after the comments I'll go with this plan:
* Debugging will work like described and will not be on by default.
* Three ways to invoke:
'use Inline Config => DEBUG => Interactive;'
'perl -MInline=DEBUG script.pl'
'export PERL_INLINE_DEBUG=Interactive'
* Other environment options:
PERL_INLINE_PAGER=less
PERL_INLINE_DEBUG_AUTO='out.make,*.c'
Cheers, Brian
--
perl -le 'use Inline C=>q{SV*JAxH(char*x){return newSVpvf
("Just Another %s Hacker",x);}};print JAxH+Perl'
