Hi, The C function PrintWarnings is currently not in the C API, but it is declared non static in the svn trunk as of revision 53110 . As this is the only function that creates the last.warning object used by the R function warnings(), I think it would be useful for programs that embed R to be able to call it. So, will it remain non static, that is callable although it's not declared in the public C API? Thanks, Jeff
Anyone have comments on this? PrintWarnings would be nice to utilize for those embedding R. Thanks, Jeff On Fri, Oct 1, 2010 at 4:49 PM, Jeffrey Horner <jeffrey.horner at gmail.com> wrote:> Hi, > > The C function PrintWarnings is currently not in the C API, but it is > declared non static in the svn trunk as of revision 53110 . As this is > the only function that creates the last.warning object used by the R > function warnings(), I think it would be useful for programs that > embed R to be able to call it. > > So, will it remain non static, that is callable although it's not > declared in the public C API? > > Thanks, > > Jeff >-- http://biostat.mc.vanderbilt.edu/JeffreyHorner
On Friday 05 November 2010, Jeffrey Horner wrote:> Anyone have comments on this? PrintWarnings would be nice to utilize > for those embedding R.I had missed your previous post. Rf_PrintWarnings is pretty useful when embedding R, indeed. We do use it in RKWard. So I would certainly appreciate if it could be promoted into the public C API. Regards Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL: <https://stat.ethz.ch/pipermail/r-devel/attachments/20101105/8deaaf3f/attachment.bin>
Apparently Analagous Threads
- Overriding InitTempDir
- Warnings created during R_eval or R_tryEval not shown before R ending or R error.
- Best way to determine if you're running 32 or 64 bit R on windows
- parse_Rd raises error when example section contains a quoted percent character
- Printing warning messages around R_tryEval