When should we use one versus the other? If I'm designing an S3 class
"blah", should I just implement
blah <- function(x, ...) UseMethod("blah")
and then a bunch of blah.whatever() functions, including blah.default()?
Or should I do
as.blah <- function(x, ...) UseMethod("as.blah")
with a bunch
My fame package has to link to the libchli.so that comes with FAME.
However, FAME is now supplying both 32 and 64 bit versions of the
library. The 32-bit version is $FAME/hli/libchli.so while the 64-bit
version is $FAME/hli/64/libchli.so. To set the right flags, it seems
that I need to know, from
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 limita
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 sectionname
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 dis
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 E
I am running into some problems with the way R CMD check looks at
documentation.
The stats::filter function returns a time series with class "ts" or
c("mts", "ts") if it is multivariate. I have created a more capable
time series class called "tis" as part of my fame package. My package
redefine
I'm writing a package that interfaces to the FAME database, via a
library of compiled C routines accessible through a Linux .so file. My
.onLoad() function loads the .so like this:
dyn.load("/opt/fame/timeiq/lib/linux_x86/libjchli.so", local = F)
and after that I also load my own fame.so via
li
I'm writing a package that I hope to make available on CRAN. The
package interfaces to the FAME database via a .so file supplied by FAME,
which should be loaded in the package .onLoad() function.
Unfortunately, so far as I know, there is no standard location where
this .so file can always be found
Full_Name: Jeff Hallman
Version: 2.4.0
OS: Linux
Submission from: (NULL) (132.200.32.34)
The window put up by tcltk::tk_select.list appears to be of fixed width (20
chars), and is not wide enough to accomodate strings longer than 20 characters
long. This can be easily fixed by setting the option
Full_Name: Jeff Hallman
Version: 2.4.0
OS: Linux
Submission from: (NULL) (132.200.32.34)
When the R Internals manual was added to the list of manuals in tkStartGUI,
whoever did it left an extra comma in the code. This creates an ugly warning
when tkStartGUI is invoked. Here is a patch file to f
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".
The documentation says "Any character
Full_Name: Jeff Hallman
Version: 2.2.0
OS: Linux
Submission from: (NULL) (132.200.32.34)
format.default() loses matrix structure if big.mark is given
> format(matrix(1:16, 4))
[,1] [,2] [,3] [,4]
[1,] " 1" " 5" " 9" "13"
[2,] " 2" " 6" "10" "14"
[3,] " 3" " 7" "11" "15"
[4,] " 4" " 8" "12"
13 matches
Mail list logo
