On Tue, 21 Jul 2015, Henrique Andrade wrote:
Dear Gretl Team,
When we use the "foreign" function and the foreign script has errors, Gretl
freezes. Please take a look at the following example:
<hansl>
open australia.gdt
foreign language=R --send-data
gretldata
end foreign
</hansl>
It works just fine. Now let's generate an intentional error using
"gretldat" instead of "gretldata":
<hansl>
open australia.gdt
foreign language=R --send-data
gretldat
end foreign
</hansl>
On a Windows PC machine the only way to make things go back to normality is
using Task Manager (CTRL-ALT-DEL) to finish Rterm. When we do this Gretl
comes back to life [;-)] and shows us the following message:
"Error in eval(expr, envir, enclos) : object 'gretldat' not found
Error executing script: halting"
Thanks for the report. The second case doesn't hang on Linux. This
seems to be an Rterm peculiarity. You're better off using Rlib, if
possible, but I guess I can study up on Rterm a little more.
Allin