Perfect! Thanks!
A.
On Wed, Jun 22, 2016 at 7:29 PM, Hadley Wickham wrote:
> Try warningcall(R_NilValue, "message")
>
> Hadley
>
>
> On Wednesday, June 22, 2016, Aaron King wrote:
>
>> I am in the midst of trying to improve error and warning messages in a
>> complex package. I find myself wa
On 22 June 2016 at 18:29, Hadley Wickham wrote:
| Try warningcall(R_NilValue, "message")
Nice one:
R> cppFunction("void foo(std::string txt) { Rf_warningcall(R_NilValue,
txt.c_str()); }")
R> foo("magic!")
Warning message:
magic!
R>
Dirk
--
http://dirk.eddelbuettel.com | @eddelbue
Try warningcall(R_NilValue, "message")
Hadley
On Wednesday, June 22, 2016, Aaron King wrote:
> I am in the midst of trying to improve error and warning messages in a
> complex package. I find myself wanting to modify R's default behavior when
> printing warnings. Specifically, it frequently h
I am in the midst of trying to improve error and warning messages in a
complex package. I find myself wanting to modify R's default behavior when
printing warnings. Specifically, it frequently happens for me that the
call that is printed with the warning message is not informative. When the
warn
