On Tue, 7 Jul 2009, Riccardo (Jack) Lucchetti wrote:
On Tue, 7 Jul 2009, Sven Schreiber wrote:
>>>> (b) are there portability problems?
>
> Again inspired from Python Zen ("Explicit is better than implicit."),
> what about using some kind of "include" statement at the top of a gretl
> script if it uses libR? That way the dependency is not buried and hidden
> and the script wouldn't fail half-way through but would refuse to run
> right from the start if R isn't present.
This is an _excellent_ idea. Even better than an "include", we may use
our "set" command. Something like
set R_support [on|off]
with "off" as the default. What do you guys think?
Yes, this is probably a good idea.
I think it's clear that we need to take some time to get this
right. I propose to leave Rlib interaction as a "hidden",
experts-only, thing in 1.8.2 (and I won't yet attempt to add it to
the Windows build). We can figure out the details for 1.8.3.
Allin.