search for: withautoprint

>>>>> Henrik Bengtsson <henrik.bengtsson at gmail.com> >>>>> on Sat, 24 Sep 2016 11:31:49 -0700 writes: > Martin, did you post your code for withAutoprint() anywhere? > Building withAutoprint() on top of source() definitely makes sense, > unless, as Bill says, source() itself could provide the same feature. I was really mainly asking for advice about the function name .. and got none. I'm now committing my version (including (some...

>>>>> William Dunlap <wdunlap at tibco.com> >>>>> on Fri, 2 Sep 2016 08:33:47 -0700 writes: > Re withAutoprint(), Splus's source() function could take a expression > (literal or not) in place of a file name or text so it could support > withAutoprint-like functionality in its GUI. E.g., >> source(auto.print=TRUE, exprs.literal= { x <- 3:7 ; sum(x) ; y <- log(x) > ;...

Martin, did you post your code for withAutoprint() anywhere? Building withAutoprint() on top of source() definitely makes sense, unless, as Bill says, source() itself could provide the same feature. To differentiate between withAutoprint({ x <- 1 }) and withAutoprint(expr) where is an expression / language object, one could have an optional...

On Sun, Sep 25, 2016 at 9:29 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>> Henrik Bengtsson <henrik.bengtsson at gmail.com> >>>>>> on Sat, 24 Sep 2016 11:31:49 -0700 writes: > > > Martin, did you post your code for withAutoprint() anywhere? > > Building withAutoprint() on top of source() definitely makes sense, > > unless, as Bill says, source() itself could provide the same feature. > > I was really mainly asking for advice about the function name > .. and got none. I missed that part. I thi...

...> FAQ Q7.22). > So you need: > print(t(tradeStats('macross'))) > if you want the output printed to the console. indeed, and "of course"" ;-) As my subject indicates, this is another case, where it would be very convenient to have a function withAutoprint() so the OP could have (hopefully) have used withAutoprint(source(..)) though that would have been equivalent to the already nicely existing source(.., print.eval = TRUE) which works via the withVisible(.) utility that returns for each 'expression' if it would auto print or not, a...

Re withAutoprint(), Splus's source() function could take a expression (literal or not) in place of a file name or text so it could support withAutoprint-like functionality in its GUI. E.g., > source(auto.print=TRUE, exprs.literal= { x <- 3:7 ; sum(x) ; y <- log(x) ; x - 100}, prompt="--> &quo...

...macross'))) >> >> > if you want the output printed to the console. >> >> indeed, and "of course"" ;-) >> >> As my subject indicates, this is another case, where it would be >> very convenient to have a function >> >> withAutoprint() >> >> so the OP could have (hopefully) have used >> withAutoprint(source(..)) >> though that would have been equivalent to the already nicely existing >> >> source(.., print.eval = TRUE) >> >> which works via the withVisible(.) utility that r...

...t; > print(t(tradeStats('macross'))) > > > if you want the output printed to the console. > > indeed, and "of course"" ;-) > > As my subject indicates, this is another case, where it would be > very convenient to have a function > > withAutoprint() > > so the OP could have (hopefully) have used > withAutoprint(source(..)) > though that would have been equivalent to the already nicely existing > > source(.., print.eval = TRUE) > > which works via the withVisible(.) utility that returns for each > 'expres...

Here is a patch to function 'stopifnot' that adds 'evaluated' argument and makes 'exprs' argument in 'stopifnot' like 'exprs' argument in 'withAutoprint'. --- stop.R 2019-05-30 14:01:15.282197286 +0000 +++ stop_new.R 2019-05-30 14:01:51.372187466 +0000 @@ -31,7 +31,7 @@ .Internal(stop(call., .makeMessage(..., domain = domain))) } -stopifnot <- function(..., exprs, local = TRUE) +stopifnot <- function(..., exprs, evaluated = F...

...;> Suharto Anggono Suharto Anggono >>>>> on Thu, 30 May 2019 14:45:22 +0000 writes: > Here is a patch to function 'stopifnot' that adds 'evaluated' argument and makes 'exprs' argument in 'stopifnot' like 'exprs' argument in 'withAutoprint'. > --- stop.R 2019-05-30 14:01:15.282197286 +0000 > +++ stop_new.R 2019-05-30 14:01:51.372187466 +0000 [..........] Thank you, Suharto. I've looked at the patch and tested it a bit, and also (re)read your April 15 remarks (cited below). I now agree that my hacks to e...

1. File is (was) saved. 2. The added code is t(tradeStats("macross")) with 2 )'s. I'd appreciate if someone with QuantStrat installed, to try this and see if they get a different result. My R and RStudio and QuantStrat libraries are all current. I get the chart and this much output. > source('~/CodingData/RCode/Quantstrat1/maCross.R') [1] "2001-06-27

1. File is (was) saved. 2. The added code is t(tradeStats("macross")) with 2 )'s. I'd appreciate if someone with QuantStrat installed, to try this and see if they get a different result. My R and RStudio and QuantStrat libraries are all current. I get the chart and this much output. > source('~/CodingData/RCode/Quantstrat1/maCross.R') [1] "2001-06-27

...FALSE) f(expression()) But, why bother making it work, while it is undocumented that 'exprs' argument in 'stopifnot' can be an expression? Well, yes, expectation may be set from the name "exprs" itself or from argument 'exprs' in function 'source' or 'withAutoprint'. Function 'withAutoprint' may be the closest match. Function 'withAutoprint' has 'evaluated' argument that controls whether work is on value of? 'exprs' or on 'exprs' as given. I like the approach. If 'E1' is an expression object, as.call(c(qu...

On Wed, 1 Apr 2015, Prof Brian Ripley wrote: &gt; I would start by trying LANGUAGE=en , e.g. More specifically, you can use en_US or en_GB. Rich [...] ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?

...been updated to detect such template leftovers, including from promptPackage(). * When S4 method dispatch fails because no method was found, the error message now includes the signature argument names; thanks to Michael Chirico's proposal on the R-devel list. * withAutoprint({ .. }) now preserves srcrefs previously lost, thanks to Andrew Simmons' report plus fix in PR#18572. * transform.data.frame() no longer adjusts names; in particular, untransformed variables are kept as-is, including those with syntactically invalid names (PR#17890)....

...been updated to detect such template leftovers, including from promptPackage(). * When S4 method dispatch fails because no method was found, the error message now includes the signature argument names; thanks to Michael Chirico's proposal on the R-devel list. * withAutoprint({ .. }) now preserves srcrefs previously lost, thanks to Andrew Simmons' report plus fix in PR#18572. * transform.data.frame() no longer adjusts names; in particular, untransformed variables are kept as-is, including those with syntactically invalid names (PR#17890)....