On Oct 7, 2014, at 7:04 AM, DataK - B. THIEURMEL wrote:
>
> Hi,
>
> With the use of R in production, it is necessary to have a system of logs
> effective, and light.
>
> Package exist as to futile.logger, but it require the additional coding of
> logs. So it is thus impossible / very difficul
esink.r
Thomas J. Leeper
http://www.thomasleeper.com
On Wed, Oct 8, 2014 at 12:00 PM, wrote:
> Message: 2
> Date: Tue, 07 Oct 2014 13:04:34 +0200
> From: "DataK - B. THIEURMEL"
> To: r-devel@r-project.org
> Subject: [Rd] [R logs] Help in develop a simply logs package
> Message
R has support for options(warning.expression=...), but it acts
differently than the options(error=...).
S (and S+) let the user override the default '.Program' expression.
Its default value was essentially
print(.Last.value <- eval(parse(file=stdin(
but a replacement could add stuff like pr
On 07/10/2014 11:11 AM, DataK - B. THIEURMEL wrote:
Do you think there is a way to apply a "global" withCallingHandlers() on
all environement / packages loaded, and then all R code will be executed
with the defined handler ?
That question makes no sense. withCallingHandlers is not applied to
On Tue, Oct 7, 2014 at 4:51 PM, Duncan Murdoch
wrote:
> On 07/10/2014 10:41 AM, DataK - B. THIEURMEL wrote:
>
>> OK, thank you for your answers. We are thus going to continue by
>> analyzing these features
>>
>
> The general outline would be this:
>
> 1. Call parse() on the whole file. This wil
Do you think there is a way to apply a "global" withCallingHandlers() on
all environement / packages loaded, and then all R code will be executed
with the defined handler ? With this way, we can define what we want for
warning, message, error, ... one time, and apply it without needed of
parse(
On 07/10/2014 10:41 AM, DataK - B. THIEURMEL wrote:
OK, thank you for your answers. We are thus going to continue by
analyzing these features
The general outline would be this:
1. Call parse() on the whole file. This will catch any syntax errors.
If it parses okay, you'll get a vector of e
OK, thank you for your answers. We are thus going to continue by
analyzing these features
Le 2014-10-07 16:29, Duncan Murdoch a écrit :
On 07/10/2014 10:16 AM, DataK - B. THIEURMEL wrote:
Thank. withCallingHandlers() and "pander::evals" seem to be very
interesting, but little adapted to the an
On 07/10/2014 10:16 AM, DataK - B. THIEURMEL wrote:
Thank. withCallingHandlers() and "pander::evals" seem to be very
interesting, but little adapted to the analysis of one or several
scripts R / of many lines of code. Our goal is one packages requiring no
modifications of code R to be able to get
On Tue, Oct 7, 2014 at 2:21 PM, Duncan Murdoch
wrote:
> On 07/10/2014, 7:04 AM, DataK - B. THIEURMEL wrote:
> > Hi,
> >
> > With the use of R in production, it is necessary to have a system of
> > logs effective, and light.
> >
> > Package exist as to futile.logger, but it require the additional
Thank. withCallingHandlers() and "pander::evals" seem to be very
interesting, but little adapted to the analysis of one or several
scripts R / of many lines of code. Our goal is one packages requiring no
modifications of code R to be able to get back all the desired
information.
Is-there a ho
On 07/10/2014, 7:04 AM, DataK - B. THIEURMEL wrote:
> Hi,
>
> With the use of R in production, it is necessary to have a system of
> logs effective, and light.
>
> Package exist as to futile.logger, but it require the additional coding
> of logs. So it is thus impossible / very difficult to use
Hi,
With the use of R in production, it is necessary to have a system of
logs effective, and light.
Package exist as to futile.logger, but it require the additional coding
of logs. So it is thus impossible / very difficult to use it with all
package them used in the calculation
Our idea is
13 matches
Mail list logo
