[Rd] Wish: more explicit error message with missing argument in c

2009-11-14 Thread Patrick Burns
Consider: c(,2) Error: argument is missing, with no default That there is no traceback is unfortunate but understandable. If such a mistake were made like this, there wouldn't be much problem. But the mistake is likely to be made in more complicated settings: rbind(c(,2), c(3,4)) Error in

[Rd] R_tryEval for OCaml-R.

2009-11-14 Thread Guillaume Yziquel
Hello. I'm currently working on the OCaml-R binding allowing to call R code from Objective Caml. As Objective Caml is a functional language, I'd like the binding to be as 'functional' as possible. Specifically, this means that I'd like using the R_tryEval function and all related entry

Re: [Rd] R_tryEval for OCaml-R.

2009-11-14 Thread Dirk Eddelbuettel
On 14 November 2009 at 16:45, Guillaume Yziquel wrote: | I'm currently working on the OCaml-R binding allowing to call R code | from Objective Caml. | | As Objective Caml is a functional language, I'd like the binding to be | as 'functional' as possible. Specifically, this means that I'd like

Re: [Rd] R_tryEval for OCaml-R.

2009-11-14 Thread Romain Francois
You can also see it in action in jri (in the Rengine.c file). http://www.rforge.net/JRI/ Romain On 11/14/2009 05:24 PM, Dirk Eddelbuettel wrote: On 14 November 2009 at 16:45, Guillaume Yziquel wrote: | I'm currently working on the OCaml-R binding allowing to call R code | from Objective

Re: [Rd] R_tryEval for OCaml-R.

2009-11-14 Thread Guillaume Yziquel
Romain Francois a écrit : You can also see it in action in jri (in the Rengine.c file). http://www.rforge.net/JRI/ Romain Thanks. I'll have a look. -- Guillaume Yziquel http://yziquel.homelinux.org/ __ R-devel@r-project.org mailing list

Re: [Rd] R_tryEval for OCaml-R.

2009-11-14 Thread Guillaume Yziquel
Dirk Eddelbuettel a écrit : On 14 November 2009 at 16:45, Guillaume Yziquel wrote: | I've had a look at R-exts.pdf, but R_tryEval is not documented. | | Could someone please point me to relevant documentation, I don't think it is documented as it is not part of the API -- see for example