similar to: utils::isS3stdGeneric chokes on primitives and identity

>>>>> Gabriel Becker writes: > I added that so I can look at the proposed fix and put it or something > similar in bugzilla for review final review. > Apologies for the oversight. Fixed now with - while(as.character(bdexpr[[1L]]) == "{") + while(is.call(bdexpr) && (as.character(bdexpr[[1L]]) == "{")) (the suggested fix does not work on

Trace adds something to the body of the function, so it does make sense that it doesn't. Whether traced functions still technically meet the definition of standard s3 generic or not is, I suppose, up for debate, but I would say that they should, I think. As before, if desired I can work on a patch for this if desired, or someone on R-core can just take care of it if that is easier. Best, ~G

Hi all, I have a patch that fixes this and also fixes/improves debugcall so that it supports pkg::fun(obj) and pkg:::fun(obj) style calls. I'm going to test it a bit more and add a regression test for isS3stdGeneric and then I will submit it to bugzilla tonight or tomorrow morning. Best, ~G On Thu, Aug 27, 2020 at 5:28 PM Gabriel Becker <gabembecker at gmail.com> wrote: > Trace

Should it work on traced functions ? As it is now it doesn't. Best, Antoine Le jeu. 20 ao?t 2020 ? 09:58, Kurt Hornik <Kurt.Hornik at wu.ac.at> a ?crit : > >>>>> Gabriel Becker writes: > > > I added that so I can look at the proposed fix and put it or something > > similar in bugzilla for review final review. > > > Apologies for the

I added that so I can look at the proposed fix and put it or something similar in bugzilla for review final review. Apologies for the oversight. ~G On Wed, Aug 19, 2020 at 3:40 PM Antoine Fabri <antoine.fabri at gmail.com> wrote: > Dear R-devel, > > utils::isS3stdGeneric tries to subset the body of the function it's fed, > primitives don't like that because they

Hello, Is there a reason for the following behaviour? > mean(c("1","2","3")) [1] NA Warning message: In mean.default(c("1", "2", "3")) : l'argument n'est ni num?rique, ni logique : renvoi de NA But: > var(c("1","2","3")) [1] 1 And also: >

I think median() behaves as designed: As long as the argument can be ordered, the "middle observation" makes sense, except when the middle falls between two categories, and you can't define and average of the two candidates for a median. The "sick man" would seem to be var(). Notice that it is also inconsistent with cov(): >

Dear r-help, Could you help me to find a solution for this error: Il y a eu 50 avis ou plus (utilisez warnings() pour voir les 50 premiers) > warnings() Messages d'avis : 1: In if ((data[pa, k] == df[, j]) & (data[ch, k] == i)) { ... : la condition a une longueur > 1 et seul le premier élément est utilisé 2: In if ((data[pa, k] == df[, j]) & (data[ch, k] == i)) { ... : la

Please note that this is documented in ?trace. "fun" is matched to what, it is a _name_ of the function to be traced, which is traced in the top-level environment. I don't know why it was designed this way, but it is documented in detail, and hence the expected behavior. Debugging is often, and also in R, implemented in the core. Tracing is implemented on top without specific

http://r.789695.n4.nabble.com/file/n3612530/PSC.r PSC.r Hi all, I just wrote a program in R by editing it in Microsoft Word and then pasting into the text editor of R. The above is the file. And below is what the console complains.... Why doesn't it recognise 'r'?? I have to mention that at least when I typed this first several lines into the console, the first error didn't

hello, > subset(swiss, Agriculture > 60 & Examination != c(14,16), select = c(Agriculture,Examination,Catholic)) Agriculture Examination Catholic Broye 70.2 16 3.30 Glane 67.8 14 4.20 Aigle 62.0 21 5.16 Avenches 60.7 19 5.23 Cossonay 69.3 22 5.62

Dear R-devel, I don't think this is expected : foo <- function() "hello" trace2 <- function(fun) trace(fun, quote(print("!!!"))) base::fun # Object with tracing code, class "functionWithTrace" # Original definition: # function() "hello" # # ## (to see the tracing code, look at body(object)) `untrace()` has the same behavior. This is

Do I understand correctly that we don't want Rd files to be valid latex ? This seems odd to me. I see that `tools::parse_Rd()` doesn't like `\verb!foo!` so maybe roxygen2 is actually doing the right thing (as opposed to just trying to) ? `parse_Rd() ` is probably what I need indeed, for some reason I hadn't found it, so that should fix my own issue here thanks a lot. Le ven. 21 juil.

Dear R-devel, I found this behavior disturbing, if `1 + f()` is called, `sys.call()` called inside of `f` will return a quoted `f()` with a "srcref" that prints "1 + f()". I don't know which one is good but I don't think they can be correct at the same time. Here's a reproducible example: f <- function(){ sc <- sys.call() print(sc) attr(sc,

I am probably mistaken but it looks to me like the design of much of the data.frame infrastructure not only does not insist you give columns names, but even has all kinds of options such as check.names and fix.empty.names https://www.rdocumentation.org/packages/base/versions/3.6.2/topics/data.frame During the lifetime of a column, it can get removed, renamed, transfomed in many ways and so on. A

>>>>> Gabriel Becker >>>>> on Thu, 2 Mar 2023 14:37:18 -0800 writes: > On Thu, Mar 2, 2023 at 2:02?PM Antoine Fabri > <antoine.fabri at gmail.com> wrote: >> Thanks and good point about unspecified behavior. The way >> it behaves now (when it doesn't ignore) is more >> consistent with data.frame() though so I

i'm trying to test the homogeneity of variance of 92 samples each one contains 3 observations. to use bartlett.test function i have created a (3,92) matrix (named xx): >bartlett.test(xx) this message appears: >Erreur dans bartlett.test.default(xx) : l'argument "g" est manquant, avec aucune valeur par d?faut when i checked the help i have understood that in g i should

Surprisingly this invalid latex syntax is still formatted "right" in the html output. On a closer look it seems like roxygen2 introduces those, when using markdown backtick quoting, if the quoted content is not syntactic. For instance: #' `c(c(1)` #' `c(c(1))` Will convert the first line to `\verb{c(c(1)}` and the second to `\code{c(c(1))}`. I've opened a ticket there FYI:

? Fri, 21 Jul 2023 15:14:09 +0200 Antoine Fabri <antoine.fabri at gmail.com> ?????: > On a closer look it seems like roxygen2 introduces those, when using > markdown backtick quoting, if the quoted content is not syntactic. For > instance: > > #' `c(c(1)` > #' `c(c(1))` > > Will convert the first line to `\verb{c(c(1)}` and the second to >

Hi everyone, I am trying to install the RMySQL package under windows xp. I've got the MySQL installed on the computer (MySQL server 5.1). I went through the steps presented on the webpage http://biostat.mc.vanderbilt.edu/wiki/Main/RMySQL and googled around and still can't find the answer. With the command readRegistry("SOFTWARE\\MySQL AB", hive="HLM", maxdepth=2) I