similar to: Should CRAN accept packages with non-R code that transcompiles into R code?

On Tue, Mar 5, 2019 at 12:52 PM Gabriel Becker <gabembecker at gmail.com> 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/S4Coffee. > > All that said, until/unless

On Tue, Mar 5, 2019 at 12:49 PM jan Vitek <vitekj at icloud.com> 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 it. Maybe, integers (rather than numerics) as

Everything is possible. One can compile C++ into JavaScript. But why? > On Mar 4, 2019, at 6:28 PM, Abs Spurdle <spurdle.a at gmail.com> 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 whether it would pass R check or not, I will

Abs (?), 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/S4Coffee. All that said, until/unless the preprocessor is officially part of the R CMD build step, what putting code like that on CRAN would look

I hope you don?t mind us using this mailing list for a small advertisement, but we think it is most relevant for this group: We'd like to invite you to RIOT 2020 - the 5rd workshop on R Implementation, Optimization and Tooling [1]. It will take place co-located with, and during, useR! 2020 in St. Louis on July 8th. RIOT is an excellent venue for deep technical discussions about R

Reasonable -- I am a co-organizer of RIOT and spent 10 years building real-time Java virtual machines. My conclusion: no one cares. :-( > On Feb 26, 2020, at 4:45 PM, Abby Spurdle <spurdle.a at gmail.com> wrote: > > If people want to create a new interpreter (for R or any other > data-driven programming language), or do something closely related > (such as adapt an existing

For the record, this is Linux R-devel: root at 4bef68c16864:~# R CMD /opt/R-devel/lib/R/bin/Rcmd: 60: shift: can't shift that many root at 4bef68c16864:~# R CMD -h /opt/R-devel/lib/R/bin/Rcmd: 62: exec: -h: not found root at 4bef68c16864:~# R CMD --help /opt/R-devel/lib/R/bin/Rcmd: 62: exec: --help: not found This is R-release on macOS: ? R CMD

I don't think anyone denies that you *could* make an EXE to do all that. The discussion is on *how easy* it should be to create a single file that contains an initial "main" function plus a set of bundled code (potentially as a package) and which when run will install its package code (which is contained in itself, its not in a repo), install dependencies, and run the main()

sorry, release "versions" On Mon, Jun 8, 2020 at 11:17 AM Abby Spurdle <spurdle.a at gmail.com> wrote: > > On Mon, Jun 8, 2020 at 4:09 AM Fox, John <jfox at mcmaster.ca> wrote: > > Does it make sense to withdraw the Windows R 4.0.1 binary until the issue is resolved? > > Yes, it does. > All the release reversions should be removed.

I see some value in Duncan?s proposal to implement this as an extra package instead of a change to base R, if only to see if the idea has legs. I?m minded to do so myself using your suggestion, but is there a particular reason why you recommend using the remotes package instead of devtools? The latter seems to have the same functions I would need, and I believe it is more widely installed that

In principle a good idea, but I'm not sure the whereabouts of Catherine Loader are known at this point. Last peeps from her on the net seem to be about a decade old. .pd > On 18 May 2020, at 10:31 , Abby Spurdle <spurdle.a at gmail.com> wrote: > > This has come up before. > > Here's the last time: > https://stat.ethz.ch/pipermail/r-devel/2019-March/077478.html

> On Jan 14, 2020, at 3:29 PM, Abby Spurdle <spurdle.a at gmail.com> wrote: > >> I do want to entice people to have a long look beyond closed >> source OS into the world of Free Software where not only R is >> FOSS (Free and Open Source Software) but (all / almost) all the >> tools you use are of that same spirit. > > And while everyone is talking about

> I have noticed a discrepancy between is.list() and is(x, ?list?) There's a similar problem with inherits(). On R 3.5.3: > f = function () 1 > class (f) = "f" > is.function (f) [1] TRUE > inherits (f, "function") [1] FALSE I didn't check what happens with: > class (f) = c ("f", "function") However, they should have the same

You could assign a density value to each point. Maybe you've done that already...? Then trim the lowest n (number of) data points Or trim the lowest p (proportion of) data points. e.g. Remove the data points with the 20 lowest density values. Or remove the data points with the lowest 5% of density values. I'll let you decide whether that is a good idea or a bad idea. And if it's a

Hello R experts, I plan to develop a tool for dynamic analysis of R programs. I would like to trace function calls at runtime, capturing argument and return values. Following a suggestion made some time ago on this list, my high-level implementation strategy is to rewrite the AST, augmenting call expressions with pre-call and post-call shims to capture the arguments and return value,

(Using R 3.5.3). I found bugs in head() and tail(). The following works: > f = function () 1 > head (f) 1 function () 2 1 However, the following does not: > class (f) = "f" > head (f) Error in x[seq_len(n)] : object of type 'closure' is not subsettable [[alternative HTML version deleted]]

Kia Ora Let's say we have: "myreplacementfunction<-" = function (..., value) { call = sys.call () print (as.list (call) ) 0 } Then we call: x = 0 myreplacementfunction (x, y, z) = 0 It will return: [[1]] `myreplacementfunction<-` [[2]] `*tmp*` [[3]] y [[4]] z $value <promise: 0x06fb6968> There's two problems here. Firstly, x has to be defined otherwise we

> My understanding is that this represents bivariate normal > approximation of the data which uses the kernel density function to > test for inclusion within a level set. (please correct me) You can fit a bivariate normal distribution by computing five parameters. Two means, two standard deviations (or two variances) and one correlation (or covariance) coefficient. The bivariate normal

> the prison made by ancient design choices That prison of ancient design choices isn't so bad. I have no further comments on object oriented semantics. However, I'm planning to follow the following design pattern. If I set the class of an object, I will append the new class to the existing class. #good class (object) = c ("something", class (object) ) #bad class (object)

I need to write some documentation: I'm looking for a standard, consistent way of referring to the components and attributes of R data structures. Googling and Stackoverflow yield a variety of github sites that do not seem to be particularly authoritative. I was hoping to find a BNF/ABNF grammar for R. I've looked at the output of bison -v ./R-3.6.2/src/main/gram.y but it does not