On 7 November 2012 at 10:16, Darren Cook wrote: | > nice to see how RInside gets even better. I saw the example of the | > "R.parseEvalQNT(cmd)". I have a question. Is it supposed to work if | > the cmd command it's correct but throws an exception (for example the | > routine crashes because has some NA data)?. | > | > If you have code that can throw you cannot use the no-throw variant | > as you would end up with undefined behaviour. | | Hello Dirk, | Where would you choose to use parseEvalQNT() instead of parseEvalQ()?
Please see examples/standard/rinside_sample14.cpp for one example. If you use the throwing variant, you "jump". | (I.e. even if you were 100% sure your code would never throw, does | parseEvalQ() have a downside?) Well "it depends" as it always does. So I provide an API with different options. You get to pick. Hth, Dirk -- Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com _______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
