similar to: Weird problem with smb 1.9.17p4 and p5

I thought R users might be interested (surprised) to hear that R will have some competition on Linux now. Bill ---------- Forwarded message ---------- Date: Sun, 24 Jan 1999 01:37:15 GMT From: Cheryl Mauer <cmauer at statsci.com> Newsgroups: comp.os.linux.announce Subject: COMMERCIAL: S-PLUS Data Analysis Software now Available on Linux Followup-To: comp.os.linux.misc -----BEGIN PGP

Kurt, if you really want to find out what things an S help file can contain, you must learn some nroff/troff [ maybe use 'groff', the GNU one ]. As always, ultimate documentation is == source. The definition of the S help is in the two files $SPLUS/cmd/help.[nt]r where nr ^= nroff, i.e. ASCII output tr ^= troff i.e. printed output (e.g via Postscript conversion) help.tr

Some people here have started using CASIM, which is an add-on we got a while back for S-Plus that allows one to spawn an S-Plus process from a C program and communicate with it. How hard do folks think it would be to develop such an interface for R? I might try it, but I'm not completely sure I'm up to it (although it would exercise my programming skills). Also, I wonder again at the

Just curious, is anyone using Samba 4.0 alpha releases in a production environment and how is it working for you? I run an environment of about 500+ Windows XP on a Netware environment and have considerable Samba 3.0 experience, but I'd like to use GPO's to control and clean up a lot of previous tech support problems. Any thoughts? Eric -- Eric J. Feldhusen Director of Technology

The R Journal home page doesn't make any promises about how frequently the journal will be published. Historically, though, there have been issues in June and December of each year. The June issue has always appeared by this time (6 August) in previous years. Has there been a change in the publication schedule? Are there still plans for a June 2016 issue? Thanks Gordon

Dear all, I'm writing to ask for advice as to best practice. A PhD student working with me is writing C++ code that we hope to make public as src code in our Bioconductor package edgeR. He wants to call the function fmm_spline, which is part of the source code for the stats package http://svn.r-project.org/R/trunk/src/library/stats/src/splines.c, from his C++ code. This function

Berton Gunter has written in part: > A few comments: > First, your remarks are interesting and, I would say, mainly well founded. However, I think they > are in many respects irrelevant, although they do point to the much bigger underlying issue, > which Roger Peng also hinted at in his reply. > I think they are sensible because R IS difficult; the documentation is often

Perhaps I've missed this in the FAQ, but has someone documented any tricks which can be used in R to optimize memory usage/execution time? For S+, StatSci used to recommend: 1. Avoid "for" loops whenever possible. 2. In "for" loops, have a simple expression, such as TRUE, as the last statement. 3. Allocate memory for a vector/array at one time, rather than building it up

I'm moving this part of an on-going discussion to r-devel because I think I've uncovered a bug: >summary.default : How is yours different from R's (I didn't try to find out) > If it has an advantage you should post to R-devel as a proposal I did propose it along time ago, but ... The fix was for a bug that Splus 3.2 and 3.3 have. It does not work properly with lists

First, let me say how glad I am to discover R! As a former user of S at the University of Toronto and, briefly S-Plus from StatSci (I had a binary version of that on Slolaris for a while), I was really glad to find the "R" project. This is perhaps not your bug, but I did have one minor glitch in compiling R. OpenBSD 2.8's math.h does not export the "struct exception"

Martin Maechler has suggested that I post this comment to r-devel. It was originally posted to bioconductor. --------------------------------- I'd like to raise the issue of a capitalization convention for naming objects in R. Almost everything in R used to be lowercase but recently there is increasing use of mixed upper/lower case to define names. There is potential for using the

This is just a suggestion/wish that it would be nice for the F-distribution functions to recognize limiting cases for infinite degrees of freedom, as the t-distribution functions already do. The t-distribution functions recognize that df=Inf is equivalent to the standard normal distribution: > pt(1,df=Inf) [1] 0.8413447 > pnorm(1) [1] 0.8413447 On the other hand, pf() will accept Inf

>[Rd] boxplot() defaults {was "boxplot in extreme cases"} >Martin Maechler maechler at stat.math.ethz.ch >Mon Nov 8 10:36:42 CET 2004 > > AndyL> Try: > > AndyL> x <- list(x1=rep(c(0,1,2),c(10,20,40)), > x2=rep(c(0,1,2),c(10,40,20))) > AndyL> boxplot(x, pars=list(medpch=20, medcex=3)) > > AndyL> (Cf ?bxp, pointed to from

In R 2.1.1, the default behaviour of scan() was changed to process all C-style escapes, even when a delimiter was specified using the 'sep' argument. A new argument 'allowEscapes' was introduced to turn this processing off. Because read.table() calls scan(), read.table() inherits the new default behaviour of scan() but without a way to turn it off. For example, reading a file

Hi Peter and others, If it helps, I wrote a small function glm.scoretest() for the statmod package on CRAN to compute score tests from glm fits. The score test for adding a covariate, or any set of covariates, can be extracted very neatly from the standard glm output, although you probably already know that. Regards Gordon --------------------------------------------- Professor Gordon K

Should R CMD check consider it an error to define a new method using setMethod for a class which is not currently defined? It seems to me that it would be best not to consider this an error. What currently happens in that setMethod issues a warning, quite correctly. This warning produces an object 'last.warning'. Then R CMD check issues a WARNING that 'last.warning' is an

I've noticed a curious interpretation of escaped characters in \examples{} in .Rd files. For example, if I type files <- dir(pattern="\\.txt") at the R prompt, I will get a vector containing all file names in the current directory containing the string ".txt". If I put \examples{ files <- dir(pattern="\\.txt") } in an .Rd file of a package,

Dear all, I am trying to write a package using formal methods and classes from the methods package. I have not been able to get the package to pass rcmd check without warnings, because rcmd check does not recognize my generic functions as code objects and therefore queries why they have documentation entries. I have isolated the problem in a very small trivial example which I give below. I

> Cleaned the DNS manually with the DNS application, but still I can't join. Same error. I thought it was the same error, but now I saw there is a small difference. It seems like a deleted object causes the problem. With "ldbsearch --cross-ncs --show-deleted .." I can see now that entry for "samba3" (beside all other demoted servers), which appears in the error message.

I am another person who has had trouble documenting S4 classes and (particularly) methods. The methods package itself is pretty cool by the way, but it is a pity that there are as yet no guidelines on S4 in the "Writing R Extensions" document. I have actually put together a guide on S4 documentation myself for the use of my own lab which is at