>
> I don't call the Execute function. fatal.epl should be opened if an error
> occures.
> In Embperl 1.3.x this worked but now Embperl 2.0b7 tries to open
"file://fatal.epl".
> Is this also a problem with the chdir?
> Or can I define the file which should be opened on error?
>
Embperl itself nev
>>First when an embperl script fails there is such a log entry:
>>[11526]Reading file://fatal.epl as input using PerlIO (0 Bytes)...
>>[11526]ERR: 12: fatal.epl(1): File file://fatal.epl open error: No such
file or
>>directory
>Embperls Execute function takes a filename and _not_ a URL. This
>First when an embperl script fails there is such a log entry:
>[11526]Reading file://fatal.epl as input using PerlIO (0 Bytes)...
>[11526]ERR: 12: fatal.epl(1): File file://fatal.epl open error: No such
file or
>directory
Embperls Execute function takes a filename and _not_ a URL. This is the
Hi!
I discovered this problem serveral times.
First when an embperl script fails there is such a log entry:
[11526]Reading //fatal.epl as input using PerlIO (0 Bytes)...
[11526]ERR: 12: fatal.epl(1): File //fatal.epl open error: No such file or
directory
I've got a fatal.epl in the same dire
