Skip to content
Prev 24607 / 63424 Next

data.frame backwards compatibility (PR#9601)

What you are reporting as missing would be *forwards* compatibility, and 
of an unstated representation (dump? save?) of objects of class 
"data.frame", not the object data.frame() itself.

The correct terminology is 'a data frame', not 'the data.frame' (which 
means something different).

No one has ever said that objects dumped/saved in future versions of R 
would be valid when restored in a current version.  How for example do you 
expect a data frame containing a raw vector to be read in a version of R 
from before the raw type was added?

You will find many instances of lack of forwards compatibility: it is 
essential to progress.
On Fri, 6 Apr 2007, v.moreno at ico.scs.es wrote:

            
That is a future version of R, so no one knows how it will behave.
1) You are asked in the FAQ not to use this address for things you are not 
'sure' are bugs.

2) This change is documented under USER-VISIBLE CHANGES, clearly 
highlighting it.
What does 'read in' mean?  load()?  source() from a dump()?
The code you used is not here, so we have no idea what you did to get that 
error.  The FAQ and the posting guide do ask for reproducible code.
Data frames always have row names (sic), by definition, and that dump 
output does show row names.  What is new is that they are allowed to be 
integers.