Skip to content

Bus error with xyplot

2 messages · Brian Ripley, Paul Murrell

#
On Mon, 3 Feb 2003, Liaw, Andy wrote:

            
It's not feasible.  If package A is upgraded and makes package B need an 
upgrade, there is no way for package B's maintainer to anticipate this.
Now one could be conservative and have B require exactly one version of A,
but then upgrading A makes B unusable.  (The latter is what has happened a 
few times with ghostscript and gsview/windvi.)

I have suggested before that grid be more closely integrated with R, and 
become a base package.  Then grid would only be changed when the R version 
changes, and the critical incompatibility goes away.

Brian
#
Hi
ripley@stats.ox.ac.uk wrote:
> I have suggested before that grid be more closely integrated with R, and
 > become a base package.  Then grid would only be changed when the R 
version
 > changes, and the critical incompatibility goes away.


Some arguments against:
(i)  grid is the only thing using (i.e., testing) large parts of the 
under-development graphics API.
(ii)  Moving grid into base would bloat base;  we're keener on making 
base more slim-line right?  (Once the API is complete, we could 
theoretically move base graphics into an add-on too.  And all the 
devices ...)
(iii)  With grid as an add-on it can have asynchronous patch versions
(iv)  In practice this is happening now anyway (new minor version of 
grid and lattice only with each minor version of R)

Paul