similar to: format.POSIXlt drops characters following percent sign (PR#8975)

On Tue, 13 Jun 2006, jhallman at frb.gov wrote: > Full_Name: Jeff Hallman > Version: 2.3.1 > OS: Windows > Submission from: (NULL) (132.200.32.34) > > > Internal(format.POSIXlt(as.POSIXlt(Sys.time()), "%Y%m%d%q", F)) > Linux R-2.2.1 returns "20060613%q". > Windows R-2.3.1 returns "20060613" dropping the "%q". There is no

Full_Name: Jeff Hallman Version: 2.0 OS: Linux Submission from: (NULL) (132.200.32.34) The function findGeneric() in the utils namespace contains this internal function: isUME <- function(e) { if (is.call(e) && (is.name(e[[1]]) || is.character(e[[1]]))) { switch(as.character(e[[1]]), UseMethod = as.character(e[[2]]), "{" =

One hassle I could do without is the necessity of writing C wrapper functions like this: void fameInit(int *status){ cfmini(status); return; } when I want to call a library function (cfmini, in this case) that takes an int argument. The .C interface only lets me pass a pointer to an int, rather than the int itself. Is there any chanch that .C could be enhanced to allow passing arguments by

Full_Name: Jeff Hallman Version: 1.2.2 OS: Solaris Submission from: (NULL) (132.200.32.33) > rle(c(1, NA, 1) $lengths [1] 3 $values [1] 1 should be as in Splus: $lengths [1] 1 1 1 $values [1] 1 NA 1 The Splus implementation (which works fine in R) is: rle <- function(x){ if(!is.atomic(x)) stop("Argument must have an atomic mode") if(length(x) == 0)

I am the maintainer of the 'tis' package. One of the functions in my package is 'nberShade'. A user wants to make nberShade generic, with the old version renamed as nberShade.default, all of which is fine with me. And he wants to add a new method, nberShade.ggplot, which works for objects of class ggplot. He also wants to add a method fortify.tis for the generic fortify defined

In the base package, as.POSIXct() is an S3 generic function, but as.POSIXlt() is not. As shown below, the current implementation is already crying out to be refactored into a generic function with methods for various classes. It calls "inherits" five times. Not only is this bad style, it also disallows me or anyone else from making as.POSIXlt() work with other kinds of time-ish

Jeffrey J. Hallman wrote: >OK, I looked at the documentation and you're right about that. However, >I'm curious about why the first argument to UseMethod is ever necessary. >Is there ever a good reason for it to be something other than the name >of the calling function? (Wouldn't that lead to confusing code?) If >not, why bother with it at all? > >I've

Full_Name: Jeff Hallman Version: 1.2.2 OS: Solaris Submission from: (NULL) (132.200.32.33) "boink<-" <- function(x, a = 1, b = 2, value){ print(match.call()) x } > z <- 1 > boink(z, b = 4) <- 22 boink<-(x = *tmp*, a = 4, value = 22) > Shouldn't it have matched the 4 to b, not a?

I have a few functions, such as screenWidth() and screenHeight(), which I have been able to implement for a Unix/Linux environment, but not for Windows. (Does anyone know how to find the screen dimensions in Windows?) The Writing R Extensions manual tells me how to include platform-specific sections in documentation, and even how to have platform-specific help files. But it doesn't say

I have an S3 class called "tis" (Time Indexed Series) which may or may not have multiple columns. I have a function "[<-.tis" that I've reproduced below. My question is this: inside of "[<-.tis", how can I distinguish between calls of the form x[i] <- someValue and x[i,] <- someValue ? In either case, nargs() is 3, and looking at the values

I have an S3 class called "tis" (Time Indexed Series) which may or may not have multiple columns. I have a function "[<-.tis" that I've reproduced below. My question is this: inside of "[<-.tis", how can I distinguish between calls of the form x[i] <- someValue and x[i,] <- someValue ? In either case, nargs() is 3, and looking at the values

>>>>> "K" == Kasper Daniel Hansen <khansen at stat.Berkeley.EDU> writes: K> On Oct 19, 2005, at 3:43 PM, Jeffrey J. Hallman wrote: K> <SNIP> >> Think about it. Once you have a basic math package that can handle >> matrix >> programming and various mathematical functions, building the various >> statistical modeling

Hi Everyone, I am uncertain that I am writing the contrast statements correctly. Basically, I'm unsure when to use a -1 and a 1 when writing the contrasts. Specifically I am interested in comparing the slopes between different temperature regimes. Temperature is therefore a factor. Time and percent are numerical. Using the gmodels package I made the following model:

In package A I have askForString(), which asks the user for a string. Also in package A I have defined ssh(), which calls askForString(). Package B has package A as a prerequisite. In package B I redefine askForString() to take advantage of a nicer user interface made available by B, namely the Emacs mini-buffer prompt. Packages B and A are both on the search path, with B ahead of A. If I call

Full_Name: Jeff Hallman Version: 2.4.1 OS: Linux Submission from: (NULL) (132.200.32.34) read.ssd() invokes PROC COPY to create an xport file, but PROC COPY has some annoying limitations that read.ssd() should deal with. The first is that PROC COPY doesn't work with member names (the sectionnames argument to read.ssd) longer than 8 characters. The second is that PROC COPY also fails if any

Is is possible from within a function to cause its caller to return()? I have a function that lets user make edits to certain objects, and then checks that the edited objects still make sense. If they don't, the function puts up a notifier that the edits are being discarded and then returns, something like: if(badEdits){ notifyDialog("bad edits will be ignored")

Full_Name: Jeff Hallman Version: 2.4.1 OS: Linux Submission from: (NULL) (132.200.32.34) When I filed this a few minutes ago, I left off the rewritten read.ssd(). I've included it at the end this time. read.ssd() invokes PROC COPY to create an xport file, but PROC COPY has some annoying limitations that read.ssd() should deal with. The first is that PROC COPY doesn't work with member

I need arguments pro-S-PLUS and against SAS for a meeting I will have next week. S-Plus is (90 - 99)% compatible with R, so using S-Plus will make things much easier for everyone. But I can't use this argument. What other arguments could I use? Alberto Monteiro

Dear All, I wonder whether anyone has an experience with FAME package written by Jeff Hallman. All my attempts to send him the following problem report did not succeed (the mail system says that my e-mail could not be delivered), so I turn for help to this list. I tried to use your FAME package written for R, but somehow I cannot get it working. I am using Windows XP and the newest R

Good morning, I use SAS and R/S-Plus as my primary tools so I have a lot of experience with these programs. By far and away, SAS is superior for handling the "messy" datasets, but also the very large ones. I work at times with datasets in the hundreds of thousands (and on occasion, millions) of records. SAS, and especially PROC SQL, are invaluable for this. But once I get to