search for: eval_langsxp

.... The first one, x, is generated through the parser of gram.c. The second one, z, is built manually, by retrieving the symbols of "str" and of "lm" via the install function. The structure of x and y are shown at the bottom of this email. Evaluating x succeeds: > # R.Raw.eval_langsxp x;; > function (formula, data, subset, weights, na.action, method = "qr", > model = TRUE, x = FALSE, y = FALSE, qr = TRUE, singular.ok = TRUE, > contrasts = NULL, offset, ...) > - : R.Raw.sexp = <abstr> > # ml_eval x;; > function (formula, data, subset,...

...n OCaml bytecode, which sorts of implies that my C glue is rather OK. From source code, the execution goes this way: > let () = ignore (R.eval_string "require(quantmod)") We're simply trying to evaluate the "require(quantmod)" string in R. > let eval_string s = eval_langsxp (parse_sexp s) eval_string calls > external parse_sexp : string -> sexp = "parse_sexp" which access the C glue code wrapping R_ParseVector. > CAMLprim value parse_sexp (value s) { > CAMLparam1(s); > SEXP text ; > SEXP pr ; > ParseStatus status; > PROT...