> 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()? (I.e. even if you were 100% sure your code would never throw, does parseEvalQ() have a downside?) Thanks, Darren Cook Director, QQ Trend http://qqtrend.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
