From b.rowlingson at lancaster.ac.uk  Fri Jan 19 19:01:56 2007
From: b.rowlingson at lancaster.ac.uk (Barry Rowlingson)
Date: Fri, 19 Jan 2007 18:01:56 +0000
Subject: [Rd] obsolescence
In-Reply-To: <Pine.LNX.4.64.0701191632430.30077@gannet.stats.ox.ac.uk>
References: <f13f1c9c0701182319r532aa912p22b3584765911884@mail.gmail.com>
	<Pine.LNX.4.64.0701191632430.30077@gannet.stats.ox.ac.uk>
Message-ID: <45B10794.3080102@lancaster.ac.uk>

Since many posts to R-devel/help invoke this response:

Prof Brian Ripley wrote:
> Please, use the current version of R and not an obselete one 

is there an argument for including a version check on R startup?  These 
things seem somewhat in vogue these days (what with everything on the 
internet being in a permanent 'beta' state), and software will often 
start up with 'A new version of Foobar is available' dialog.

  Perhaps R.version could return a component that says 'current', 
'buggy', or 'obsolete' as appropriate?

  It would need a file on a well-known URL to give the version 
information, an internet connection, and a bit of R code.  And obviously 
a server capable of handling the load...

  I'd vote to have the version check off by default, perhaps settable at 
compile-time, and configurable by the usual R startup mechanism.  The 
check wouldn't run if R is running with the BATCH command.  Personally, 
I'd switch it off completely, because these things annoy me.

  Maybe this is already in R, but I'm using an obsolete version at the 
moment (2.4.0).

Barry



[Rd] obsolescence
Barry Rowlingson