> Finally, for your specific use case, see also ?withCallingHandlers which
> can not only detect warnings, but also set callback functions which can
> decide whether to abort or process and restart when a warning is thrown.
> The documentation for that function is a little rough, though you can see
Elad,
I disagree. This section:
It is undocumented where last.warning is stored nor that it is
visible, and this is subject to change. Prior to R 2.4.0 it was
stored in the workspace, but no longer.
already says that it won't work (or rather that there is no reason to think
it would
Hi Scott,
options(warn = 2) is a great idea. Thank you. My suggestion was not to
change the behavior of last.warning, just to write what the behavior is
very explicitly in the help page. But I guess this is just difference of
opinions.
Thanks for the suggestions,
Elad
On Sun, Dec 29, 2013 at 3:
On Sat, Dec 28, 2013 at 11:19 PM, Elad Zippory wrote:
> Hi Scott,
>
> Thank you for your detailed response. (btw, the reason why I didn't link the
> Stack Overflow question is because I deleted it after I sent the e-mail).
Hi Elad,
Please keep the conversation on the list unless there is a reaso
On Sat, Dec 28, 2013 at 6:06 PM, Elad Zippory wrote:
> Hi,
>
> I raised this issue at stackoverflow and it was suggested to raise it here:
>
> >From the current help page, it is unclear that "warnings()" does not clear
> after rm(list=ls()). Currently the page states that:
>
> "Warning: It is undo
Hi,
I raised this issue at stackoverflow and it was suggested to raise it here:
>From the current help page, it is unclear that "warnings()" does not clear
after rm(list=ls()). Currently the page states that:
"Warning: It is undocumented where last.warning is stored nor that it is
visible, and t
