Displaying 8 results from an estimated 8 matches for "inerror".
Did you mean:
i_error
2019 Jul 13
2
Mitigating Stalls Caused by Call Deparse on Error
..., meaning \code{.Traceback}), or an
Index: src/main/errors.c
===================================================================
--- src/main/errors.c?? ?(revision 76827)
+++ src/main/errors.c?? ?(working copy)
@@ -1008,7 +1008,7 @@
??? ??? (which should not happen) */
??? ?if (traceback && inError < 2 && inError == oldInError) {
??? ???? inError = 2;
-?? ???? PROTECT(s = R_GetTraceback(0));
+?? ???? PROTECT(s = R_GetTracebackParsed(0));
??? ???? SET_SYMVALUE(install(".Traceback"), s);
??? ???? /* should have been defineVar
??? ??????? setVar(install(".Traceback"...
2005 Oct 17
1
RFC: API to allow identification of warnings and errors in the output stream
...ctly backwards compatible.
Of course, the naming may not be perfect?
2) While 1 makes it easy to split warning _and_ errors (and messages) from
regular output, it does not suffice to differentiate _between_ warnings,
errors, and messages on the error channel. The patch addresses this, by
making inError, inWarning, and inPrintWarnings from errors.c accessible
(read-only) in R_ext/Error.h.
This part of the patch may be slightly more delicate, in that inError,
inWarning, and inPrintWarnings seem to be more internal status indications.
So the question is: Are those potentially subject to change, i...
2005 Oct 10
2
Catching warning and error output
Hi all,
I'm working on a GUI frontend for R, and I'm looking for a good way to catch
all warning- and error-output. The reason for this is mostly, that I would
like to know, which sections of the output are "normal" output, warnings, and
errors. This would allow for some nice features, such as highlighting
warnings and errors in a different color, or popping up a message
2019 Jul 14
2
[External] Mitigating Stalls Caused by Call Deparse on Error
...> Index: src/main/errors.c
> ===================================================================
> --- src/main/errors.c?? ?(revision 76827)
> +++ src/main/errors.c?? ?(working copy)
> @@ -1008,7 +1008,7 @@
> ??? ??? (which should not happen) */
> ??? ?if (traceback && inError < 2 && inError == oldInError) {
> ??? ???? inError = 2;
> -?? ???? PROTECT(s = R_GetTraceback(0));
> +?? ???? PROTECT(s = R_GetTracebackParsed(0));
> ??? ???? SET_SYMVALUE(install(".Traceback"), s);
> ??? ???? /* should have been defineVar
> ??? ??????? setVar...
2019 Jul 16
1
[External] Mitigating Stalls Caused by Call Deparse on Error
...===============================================================
>>> --- src/main/errors.c (revision 76827)
>>> +++ src/main/errors.c (working copy)
>>> @@ -1008,7 +1008,7 @@
>>> (which should not happen) */
>>> if (traceback && inError < 2 && inError == oldInError) {
>>> inError = 2;
>>> - PROTECT(s = R_GetTraceback(0));
>>> + PROTECT(s = R_GetTracebackParsed(0));
>>> SET_SYMVALUE(install(".Traceback"), s);
>>> /* should hav...
2019 Jul 14
0
[External] Mitigating Stalls Caused by Call Deparse on Error
...> Index: src/main/errors.c
> ===================================================================
> --- src/main/errors.c?? ?(revision 76827)
> +++ src/main/errors.c?? ?(working copy)
> @@ -1008,7 +1008,7 @@
> ??? ??? (which should not happen) */
> ??? ?if (traceback && inError < 2 && inError == oldInError) {
> ??? ???? inError = 2;
> -?? ???? PROTECT(s = R_GetTraceback(0));
> +?? ???? PROTECT(s = R_GetTracebackParsed(0));
> ??? ???? SET_SYMVALUE(install(".Traceback"), s);
> ??? ???? /* should have been defineVar
> ??? ??????? setVar...
2019 Jul 15
0
[External] Mitigating Stalls Caused by Call Deparse on Error
...rors.c
>> ===================================================================
>> --- src/main/errors.c?? ?(revision 76827)
>> +++ src/main/errors.c?? ?(working copy)
>> @@ -1008,7 +1008,7 @@
>> ??? ??? (which should not happen) */
>> ??? ?if (traceback && inError < 2 && inError == oldInError) {
>> ??? ???? inError = 2;
>> -?? ???? PROTECT(s = R_GetTraceback(0));
>> +?? ???? PROTECT(s = R_GetTracebackParsed(0));
>> ??? ???? SET_SYMVALUE(install(".Traceback"), s);
>> ??? ???? /* should have been defineVar
>...
2002 Aug 22
0
R_Interactive decision to halt execution during errors
Hi,
I'm currently trying to use R as a back-end from an interface (you may have
seen me on the help list), and I'm running into something that is rather
confusing. The following lines in main/errors.c of R 1.5.1:
439: if ( !R_Interactive && !haveHandler && inError ) {
440: REprintf("Execution halted\n");
441: R_CleanUp(SA_NOSAVE, 1, 0); /* quit, no save, no .Last, status=1
*/
442: }
Which seems to not make any sense at all. I've scoured the code and can't
figure out what the rationale is for halting execution simply beca...