What the file and require does is to allow the Perl debugger to
usefully display the Perl content.
When run with eval, the Perl debugger just shows blank code.
I did seem to think, for some reason, that it didn't delete the
require'd file until the end of the process though, I'll check that.
Adam K
2009/9/5 Peter Makholm via RT <bug-ORLite@rt.cpan.org>:
Show quoted text> Fri Sep 04 11:10:26 2009: Request 49432 was acted upon.
> Transaction: Ticket created by pmakholm
> Queue: ORLite
> Subject: Enabling debug wrongly claims to store generated code
> Broken in: 1.25
> Severity: Unimportant
> Owner: Nobody
> Requestors: peter@makholm.net
> Status: new
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=49432 >
>
>
> While loading ORLite with debug enabled teh generated code is evaluated
> with the dval subroutine. This subroutine claims that the code is saved i
> a tempfile but this file is unlinked right after it is 'required'.
>
> This basically renders the use of a tempfile and 'require' meaningless
> over the use of eval in the non-debug case.
>
> It would be nice if the generated code wasn't unlinked.
>
