Am 09.07.2009 22:01, Allin Cottrell schrieb:
I'm not trying to pre-empt further discussion of gretl/R
interaction, but I'd like to get the Rlib material into a state
where I'm reasonably comfortable with it, on a provisional and
still hidden basis. So I've been doing a bit more.
.... [details]
sounds good!
If you try to "set R_lib on" and there's no Rlib support in gretl,
you get a warning:
Warning: setting ignored: 'R_lib' not supported.
Maybe an error (aborting the script) would be better? At least that's
how my suggestion was intended: don't even try to run a script that
depends on R_lib if it doesn't exist on the machine.
At some point it may be worth reversing the default: in other
words, using Rlib automatically for "foreign language=R" if it's
supported by the build, unless the user does "set Rlib off".
Or we could trash the option. For the moment I want it there for
testing purposes.
Similarly, I think it would actually be good to have it there forever,
e.g. for transparency/explicitness.
Then there's the last point: look-up of R functions. For the
present I've left this as I last described it. You have to "set
R_functions" on to get this. This depends on compiled-in Rlib
support, but it does not depend on setting "R_lib" on. And you
need to prepend "R_" to the function names to have them found.
Ah, well maybe this option then does what I had in mind for the R_lib
option. So consider my comments above with this caveat.
If anyone's still reading: I've also implemented support for
"foreign language=ox" (and editing/running of Ox programs via the
GUI). But this is not enabled by default in the gretl build:
you have to select --with-ox when configuring gretl to get it.
Of course also nice to have; but may I remind people [slightly OT] that
Ox is free only for educational institutions. The license explicitly
says that it's not free even for non-profit or governmental organizations.
cheers,
sven