similar to: function remains loaded in the search space after detaching the package

Dear all, I'm getting more and more frustrated with the whole S4 thing and I'm looking for a more advanced summary on how to deal with them. Often I get error messages that don't make sense at all, or the code is not doing what I think it would do. Far too often inspecting the code requires me to go to the source, which doesn't really help in easily finding the bit of code

Thank you gents, I overlooked the subtle differences. On Tue, Mar 28, 2017 at 2:49 PM, Lukas Stadler <lukas.stadler at oracle.com> wrote: > ?typeof? is your friend here: > > > typeof(`[`) > [1] "special" > > typeof(mc[[1]]) > [1] "symbol" > > typeof(mc2[[1]]) > [1] "special" > > so mc[[1]] is a symbol, and thus not a

?typeof? is your friend here: > typeof(`[`) [1] "special" > typeof(mc[[1]]) [1] "symbol" > typeof(mc2[[1]]) [1] "special" so mc[[1]] is a symbol, and thus not a primitive. - Lukas > On 28 Mar 2017, at 14:46, Michael Lawrence <lawrence.michael at gene.com> wrote: > > There is a difference between the symbol and the function (primitive >

Dear all, I want to apply a function to list elements, two by two. I hoped that combn would help me out, but I can't get it to work. A nested for-loop works, but seems highly inefficient when you have large lists. Is there a more efficient way of approaching this? # Make some toy data data(iris) test <- vector("list",3) for (i in 1:3){ x <- levels(iris$Species)[i] tmp

There is a difference between the symbol and the function (primitive or closure) to which it is bound. This: mc2 <- as.call(list(`[`,iris,2,"Species")) Evaluates `[` to its value, in this case the primitive object, and the primitive itself is incorporated into the returned call. If you were to do this: mc2 <- as.call(list(quote(`[`),iris,2,"Species")) The `[` would

Dear, I have noticed this problem while looking at the following question on Stackoverflow : http://stackoverflow.com/questions/42894213/s4-class-subset-inheritance-with-additional-arguments While going through callNextMethod, I've noticed the following odd behaviour: mc <- call("[",iris,2,"Species") mc[[1]] ## `[` is.primitive(`[`) ## [1] TRUE

Dear R People: If I put in: > findPerl Error: object 'findPerl' not found But if I use: > gdata:::findPerl function (perl, verbose = "FALSE") { errorMsg <- "perl executable not found. Use perl= argument to specify the correct path." if (missing(perl)) { perl = "perl" } perl = Sys.which(perl) if (perl == "" ||

> On 31 May 2017, at 16:40 , Joris Meys <jorismeys at gmail.com> wrote: > > And with "equally spaced" I obviously meant "of equal size". It's getting > too hot in the office here... We have a fair amount of cool westerly wind up here that I could transfer to you via WWTP (Wind and Weather Transport Protocol). If you open up a sufficiently large pipe,

And with "equally spaced" I obviously meant "of equal size". It's getting too hot in the office here... On Wed, May 31, 2017 at 4:39 PM, Joris Meys <jorismeys at gmail.com> wrote: > Seriously, if a method gives a wrong result, it's wrong. line() does NOT > implement the algorithm of Tukey, even not after the patch. We're not > discussing Excel here,

Dear all, I have a problem with the function read.xls from the gdata package, error message see below. Two examples: First, I try to read my data, which does not work; Secondly, I tried the example code/data with the Iris data, which worked Any idea? Thanks, Lars > path<-"I:/subProjects/bh/HPGD/" > > setwd(path) > > xls <- "Platten_Liste_090421.xls"

Can anyone help me how to read xls file into R. I have tried following library(gdata) xlsfile <- file.path(.path.package('gdata'),'xls','iris.xls') read.xls(xlsfile) I got following error: Converting xls file to csv file... Error in system(cmd, intern = !verbose) : perl not found Error in file.exists(tfn) : invalid 'file' argument Question *1) What is the way

> On 18 May 2017, at 14:51, peter dalgaard <pdalgd at gmail.com> wrote: > > >> On 18 May 2017, at 13:47 , Joris Meys <jorismeys at gmail.com> wrote: >> >> Correction: Also dlt uses the default timezone, but POSIXlt is not recalculated whereas POSIXct is. Reason for that is the different way values are stored (hours, minutes, seconds as opposed to minutes

Thank you for the insights. I understood as much from the code, but I can't really see how this can cause a problem when using with() or within() within a package or a function. The environments behave like I would expect, as does the evaluation of the arguments. The second argument is supposed to be an expression, so I would expect that expression to be evaluated in the data frame first. I

Correction: Also dlt uses the default timezone, but POSIXlt is not recalculated whereas POSIXct is. Reason for that is the different way values are stored (hours, minutes, seconds as opposed to minutes from origin, as explained in my previous mail) CHeers Joris On Thu, May 18, 2017 at 1:45 PM, Joris Meys <jorismeys at gmail.com> wrote: > This has to do with your own timezone. If I run

On 01/04/2015 2:33 PM, Joris Meys wrote: > Thank you for the insights. I understood as much from the code, but I > can't really see how this can cause a problem when using with() or > within() within a package or a function. The environments behave like > I would expect, as does the evaluation of the arguments. The second > argument is supposed to be an expression, so I

Hi Duncan, that explains, thank you. If nobody finds the time to fix that, I might give it a shot myself this summer. Barbeque is overrated. Cheers Joris On Tue, May 23, 2017 at 3:10 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 23/05/2017 8:39 AM, Joris Meys wrote: > >> Hi all, >> >> Don't know if this is a known issue, but I couldn't find

> On 18 May 2017, at 14:58 , Martyn Plummer <plummerM at iarc.fr> wrote: > > > >> On 18 May 2017, at 14:51, peter dalgaard <pdalgd at gmail.com> wrote: >> >> >>> On 18 May 2017, at 13:47 , Joris Meys <jorismeys at gmail.com> wrote: >>> >>> Correction: Also dlt uses the default timezone, but POSIXlt is not recalculated

Le 31/05/2017 ? 16:39, Joris Meys a ?crit : > Seriously, if a method gives a wrong result, it's wrong. I did not understand why you and others were using term "wrong" based on something that I was considering as just "different" implementation. More thorough reading revealed that I have overlooked this phrase in the line's doc: "left and right /thirds/ of the

I've noticed that I get a warning message every time a package masks some functions from Hmisc. The warning message says : Warning message: In identical(get(., i), get(., lib.pos)) : ignoring non-pairlist attributes This happens with eg: library(plyr) library(xtable) I think I've seen this passing by before, but I'm not sure any more. Just thought I'd mention it. Cheers Joris

The key difference being that while not under the GPL, highcharter is still open source. There isn't a single compiled library in the entire package. WinBUGS otoh is closed source (although there is an open source version of it, OpenBUGS). As far as I understood, CRAN doesn't accept packages containing any binary executable code without the proper source files attached. So including the