Displaying 6 results from an estimated 6 matches for "rprint".
Did you mean:
print
2019 Sep 15
2
REprintf could be caught by tryCatch(message)
Dear R-devel community,
There appears to be an inconsistency in R C API about the exceptions
that can be raised from C code.
Mapping of R C funs to corresponding R functions is as follows.
error -> stop
warning -> warning
REprintf -> message
Rprintf -> cat
Rprint/cat is of course not an exception, I listed it just for completeness.
The inconsistency I would like to report is about REprintf. It cannot
be caught by tryCatch(message). Warnings are errors are being caught
as expected.
Is there any chance to "fix"/"improve&quo...
2019 Sep 15
2
[External] REprintf could be caught by tryCatch(message)
...ng R functions is as follows.
> >
> > error -> stop
> > warning -> warning
> > REprintf -> message
>
> This is wrong: REpintf is like cat with file = stderr(). If this claim
> is made somewhere in R documentation please report it a a bug.
>
> > Rprintf -> cat
> >
> > Rprint/cat is of course not an exception, I listed it just for completeness.
> > The inconsistency I would like to report is about REprintf. It cannot
> > be caught by tryCatch(message). Warnings are errors are being caught
> > as expected.
> >...
2019 Sep 15
0
[External] REprintf could be caught by tryCatch(message)
...de.
> Mapping of R C funs to corresponding R functions is as follows.
>
> error -> stop
> warning -> warning
> REprintf -> message
This is wrong: REpintf is like cat with file = stderr(). If this claim
is made somewhere in R documentation please report it a a bug.
> Rprintf -> cat
>
> Rprint/cat is of course not an exception, I listed it just for completeness.
> The inconsistency I would like to report is about REprintf. It cannot
> be caught by tryCatch(message). Warnings are errors are being caught
> as expected.
>
> Is there any chance to...
2006 Jan 12
1
Checksum of a file
Hi all,
With reference to the mail subjected : IO Timeout Error in file less than 3 MB,
thanks to Wayne Davison and Tony for having suggested the changes to be done.
I have moved to rsync version 2.6.6 from the 2.4 series.
As per my project requirement, i need to know the checksum of the file being synced.
For this purpose i tried debugging the code. I understand that rsync breaks the
2019 Sep 16
0
[External] REprintf could be caught by tryCatch(message)
...gt;>>
>>> error -> stop
>>> warning -> warning
>>> REprintf -> message
>>
>> This is wrong: REpintf is like cat with file = stderr(). If this claim
>> is made somewhere in R documentation please report it a a bug.
>>
>>> Rprintf -> cat
>>>
>>> Rprint/cat is of course not an exception, I listed it just for completeness.
>>> The inconsistency I would like to report is about REprintf. It cannot
>>> be caught by tryCatch(message). Warnings are errors are being caught
>>> as exp...
2007 Oct 10
0
patch for rsync: provides "nice = N" option
...ore giving up root permissions, check for errors, probably
get it wrong sometimes, and it seems so much easier to allow only
the behavior which the patch intended to add anyway: lower the
priority.
The only thing I'm not completely sure about is how to best do
logging. I have two calls to rprint(FLOG, ...): one is for an
error condition (providing a negative nice), and the other is
just an info notice.
rprintf(FLOG, "WARNING: nice(%d) not allowed (must be positive) on module %s\n",
niceval, name);
rprintf(FLOG, "rsync set nice(%d) on module %s\n", niceval, name)...