G'day all,
I have daily scripts running to install the patched version of the
current R version and the development version of R on my linux box
(Ubuntu 18.04.2 LTS).
The last development version that was successfully compiled and
installed was "R Under development (unstable) (2019-02-25 r76159)"
Posted this to r-sig-mixed-models
(https://stat.ethz.ch/pipermail/r-sig-mixed-models/2019q1/027620.html) but this
might rather need to go to r-devel anyway, so reposting here:
I came across a weird problem / bug with augPred() from nlme (nlme_3.1-137).
Here is a reproducible example to illustra
> Berwin A Turlach
> on Tue, 5 Mar 2019 16:54:09 +0800 writes:
> G'day all,
> I have daily scripts running to install the patched version of the
> current R version and the development version of R on my linux box
> (Ubuntu 18.04.2 LTS).
> The last development ver
On 05/03/2019 08:54, Berwin A Turlach wrote:
G'day all,
I have daily scripts running to install the patched version of the
current R version and the development version of R on my linux box
(Ubuntu 18.04.2 LTS).
The last development version that was successfully compiled and
installed was "R Un
> Martin Maechler
> on Tue, 5 Mar 2019 12:45:36 +0100 writes:
> Berwin A Turlach
> on Tue, 5 Mar 2019 16:54:09 +0800 writes:
>> G'day all,
>> I have daily scripts running to install the patched version of the
>> current R version and the development version o
Another possible shortcut definition:
assert <- function(exprs)
do.call("stopifnot", list(exprs = substitute(exprs), local = parent.frame()))
After thinking again, I propose to use
stop(simpleError(msg, call = if(p <- sys.parent()) sys.call(p)))
- It seems that the call is the call of th
> Suharto Anggono Suharto Anggono
> on Tue, 5 Mar 2019 17:29:20 + writes:
> Another possible shortcut definition:
> assert <- function(exprs)
> do.call("stopifnot", list(exprs = substitute(exprs), local =
parent.frame()))
Thank you. I think this is mostly a matter
Hi Paul,
Great, thank you for looking in to this, and I'm glad that you're able to
reproduce it at your end too.
>From your reply, I'm happy that it seems like the fix may be fairly trivial,
>but I understand the necessity for caution.
If there's anything else I can do to help, please do let m
Everything is possible. One can compile C++ into JavaScript.
But why?
> On Mar 4, 2019, at 6:28 PM, Abs Spurdle wrote:
>
> It may be possible to create an R-like programming language that
> transcompiles into R code (or otherwise constructs R objects and calls
> R functions).
>
> I'm not sure
Hi,
I think I've discovered a bug in base R.
Basically, when using 'Inf' as as 'Date', is is visually displayed as
'NA', but R still treats it as 'Inf'. So it is very confusing to work
with, and can easily lead to errors:
# Visually displays as NA
> as.Date(Inf, origin="2018-01-01")
[1] NA
On Tue, Mar 5, 2019 at 12:49 PM jan Vitek wrote:
> Everything is possible. One can compile C++ into JavaScript.
>
> But why?
>
>
I would like to support Java style syntax for class definitions.
(Then it could transcompile into either S3 or S4).
And possibly change some other things while I'm at
On Tue, Mar 5, 2019 at 12:52 PM Gabriel Becker
wrote:
> I have thought about and have (somewhere "up near the top" of my todo
> list) prototyping a preprocessor for R, and I have relevant code that emits
> (transpiles, in a way) structured comments into S4 code in
> https://github.com/gmbecker/S4
As long as the semantic models are close, then such a translation is
possible and not even very difficult. Syntactic sugar is cheap.
The challenge that you will run into is that there is a temptation
to change the semantics when designing a new language. R has many
warts that, if one were to start
On Tue, Mar 5, 2019 at 12:41 PM Abs Spurdle wrote:
>
>
> On Tue, Mar 5, 2019 at 12:52 PM Gabriel Becker
> wrote:
>
>> I have thought about and have (somewhere "up near the top" of my todo
>> list) prototyping a preprocessor for R, and I have relevant code that emits
>> (transpiles, in a way) str
Richard,
Well others may chime in here, but from a mathematical point of view, the
concept of "infinite days from right now" is well-defined, so it maybe a
"valid" date in that sense, but what day and month it will be (year will be
Inf) are indeterminate/not well defined. Those are rightfully, NA,
format.Date runs into trouble long before Inf:
> as.Date("2018-03-05") + c(2147466052, 2147466053)
[1] "5881580-07-11" "-5877641-06-23"
Bill Dunlap
TIBCO Software
wdunlap tibco.com
On Tue, Mar 5, 2019 at 2:33 PM Gabriel Becker wrote:
> Richard,
>
> Well others may chime in here, but from
Hi Gabriel,
The point is that it *visually* displays as NA, but is.na() still
responds as FALSE.
When I (and I am sure many people) see an NA, we then use is.na(). If we
see Inf displayed, we then use is.infinite(). With as.Date() this breaks
down.
I'm not arguing that as.Date(Inf) should be
On Tue, Mar 5, 2019 at 9:54 PM Richard White wrote:
> Hi Gabriel,
>
> The point is that it *visually* displays as NA, but is.na() still
> responds as FALSE.
>
> When I (and I am sure many people) see an NA, we then use is.na(). If we
> see Inf displayed, we then use is.infinite(). With as.Date()
18 matches
Mail list logo