similar to: answering my own question

In Version 0.64.1 (May 8, 1999), Solaris 2.5.1, expression(theta^{-}) and expression(theta^{+}) (and the equivalent subscripts) give syntax errors. (Superscript or subscripts of numbers, letters, or "+1" or "-1" all work.) Anyone have a workaround or a patch? Or should I just use psfrag as god intended? Ben Benjamin Bolker Dep't

In Version 0.64.1 (May 8, 1999), Solaris 2.5.1, expression(theta^{-}) and expression(theta^{+}) (and the equivalent subscripts) give syntax errors. (Superscript or subscripts of numbers, letters, or "+1" or "-1" all work.) Anyone have a workaround or a patch? Or should I just use psfrag as god intended? Ben Benjamin Bolker Dep't

I was translating some code from C to R and found that I would really like to be able to pass some parameters to an R function by reference (i.e., have the function make changes in the variables that then propagate back to the calling environment). I have some vague knowledge of the whole assign(substitute(deparse())) framework, but I was just wondering if there is some simpler/more accepted

I've been happily using R on SunOS/Solaris for a while, but am now trying to develop some course work on Windows. I know the real action is on Win32, but I have access to a laptop which runs 3.1 and I thought it might be useful to develop on the lowest common denominator anyway. I downloaded "tmp.zip" (dated 03 September 1998) from /R/CRAN/bin/windows/windows, which unzipped to

I've noticed a few minor annoyances/mismatches with S in image(). First, if you give it just a matrix argument (image(z)), it complains rather than (as S does) using default x and y. This patch fixes it to work (mostly) like S (although in keeping with what was in R already the default x,y coordinates are ((0,1),(0,1)) rather than (1:nrow,1:ncol)). 5,16d4 < if(is.list(x)) {

Is this behavior correct? (R 0.49 on SunOS 4.1.4) > "a">1 TRUE > "a"<1 FALSE > "a"==1 FALSE > "a">2 TRUE > "a"<2 FALSE (I know, this is like the old joke: "Doctor, it hurts when I do this." "Well, don't do that!" But it might be useful to have this caught by an error or warning message

I don't have time to track this down right now -- if no-one does it in the next few days before I finish the current piece of work I will try to find it myself. R gets the wrong answer for the eigensystem of a (particular) 4x4 matrix (SunOS 4.1.4). Running these commands: x _ matrix( c(-10, 0 ,0 ,0, 0 ,-0.3 ,0 ,0, 1 , 0.03 ,-0.594,0.0020,

In the future (say after release 0.5 goes out), would it be feasible to start a publically-accessible list of bug reports, known bugs, and patches? (Something like the current TASKS list, but maybe a little bit more dynamic?) Benjamin Bolker Dep't of Ecology and Evolutionary Biology, ben@eno.princeton.edu Princeton University tel: (609) 258-6886, fax: (609) 258-1334

In the future (say after release 0.5 goes out), would it be feasible to start a publically-accessible list of bug reports, known bugs, and patches? (Something like the current TASKS list, but maybe a little bit more dynamic?) Benjamin Bolker Dep't of Ecology and Evolutionary Biology, ben@eno.princeton.edu Princeton University tel: (609) 258-6886, fax: (609) 258-1334

In the future (say after release 0.5 goes out), would it be feasible to start a publically-accessible list of bug reports, known bugs, and patches? (Something like the current TASKS list, but maybe a little bit more dynamic?) Benjamin Bolker Dep't of Ecology and Evolutionary Biology, ben@eno.princeton.edu Princeton University tel: (609) 258-6886, fax: (609) 258-1334

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

[ SunOS 4.1.3, R-0.50-a1; I'm mostly very pleased, I haven't been pounding on it as hard as some folks have ] par(lwd) seems to be a bit of a stub right now; I wouldn't necessarily expect it to do anything in the x11() driver (nor would I know how to fix it), but it would be nice in the postscript driver (e.g. for thick lines for things to be made into slides). I will try to

Responding to my own post, after some hacking: To fix the behavior of the following test code (the rect()s inherit the lty set by the previous abline())-- x _ (1:100)/10 plot(x,sin(x)) abline(h=0,lty=2,col="red") rect(1,0,2,0.5) abline(v=2) rect(3,0,4,0.5) Here are some diffs (now all I have to do is wade through and get lwd working properly ...) *** devX11.c.orig Tue Jul 29

forgot to fix psx11.c and devPicTeX.c while I was at it (devPicTeX.c doesn't seem to change the color). Should psx11.c be devpsx11.c? Diffs: *** psx11.c.orig Wed Jul 30 10:08:48 1997 --- psx11.c Wed Jul 30 10:09:10 1997 *************** *** 293,298 **** --- 293,299 ---- } if(fg != NA_INTEGER) { psx11_SetColor(fg); + psx11_SetLinetype(GP->lty); PostScriptOpenRectangle(psfp,

box() doesn't appear to do anything with the "col=" parameter (it does use "lwd=" correctly). I may fix this if I get around to it, for now I'll probably hack PostScript. (Thanks, everyone, for all the work on R: I look forward to the spiffy graphics once the "new and interesting bugs" are somewhat tamed ...) Benjamin Bolker Dep't of Ecology

Just a quick report on compiling R 0.62.3 for SunOS 4.1.4 and Solaris 2.6 (both with gcc 2.7.2.something), in hopes that it'll be useful to someone. 4.1.4 - I followed Charles Berry's forward of Ross Ihaka's suggestion about putting fake #defines for gamma and lgamma in src/include/Mathlib.h (this works best on the second pass, after the graphics library (which also contains

I decided I wanted an "infinity" in some label text. Many of these symbols should probably be incorporated in a different way, but they don't seem to do any harm as is. *** plotmath.c.orig Fri Sep 25 17:21:33 1998 --- plotmath.c Fri Sep 25 17:46:57 1998 *************** *** 183,188 **** --- 183,232 ---- "psi", 121, "zeta", 122, + "therefore",

Some of these I can implement pretty easily myself, others are harder ... GRAPHICS: - a new option(), "plot.type", that allows one to set the default plot type for pairs of points to something other than "p"; - the ability to set just the lower or upper limits on an axis and have the other limit auto-scaled (somewhat trickier: I don't know the most convenient way

matplot doesn't seem to pass through options like lwd, cex, etc. quite the way I'd like. I've thought of two ways to fix this, I don't know which is better. The first is to treat lwd, cex, etc., exactly like the other options (col, lty ...) -- (these diffs are long, skip down two pages if you want to see the other way) *** matplot.orig Tue Jan 13 18:17:54 1998 ---

I've recently tried to get 0.62.3 up on our Suns (4.1.4, using gcc; I'm also having trouble with a Solaris 2.6 compile but I haven't given up hope on that one yet) -- the last compile I did was 0.61.1, which worked smoothly. Running ./configure --prefix=/usr/local/apps/R/R-0.62.3 [--with-g77] (tried both with and without g77, eventually get to the same place), I get a conflict