Also, if it it adds any value to what you are looking for, the output
of serialize() also has header information, cf. R-devel thread 'Small
inconsistency in serialize() between R versions and     implications on
digest()' started March 7, 2007:

  http://www.mail-archive.com/r-devel@r-project.org/msg07931.html

It caused us some headaches when trying to generate identical output
of the same input using different versions of R.  It was solved in
that thread.  See code for digest::digest() on how to skip/ignore that
header.

/Henrik


On Mon, Feb 7, 2011 at 1:51 PM, Prof Brian Ripley <rip...@stats.ox.ac.uk> wrote:
> On Mon, 7 Feb 2011, Hadley Wickham wrote:
>
>> Hi all,
>>
>> Is there any relationship between save and serialize?  Do they use the
>> same algorithm?
>
> See the R-internals manual: there is more info in the R-devel version, not
> least because saveRDS() is added to the mix.
>
> But basically serialize() and saveRDS() use the same format, and save()
> writes a header and then serializes a pairlist of the objects given.
>
> 'The same algorithm' is somewhat misleading here: strictly no, as they
> manage to use four entry points to the code base.
>
>>
>> Hadley
>>
>> --
>> Assistant Professor / Dobelman Family Junior Chair
>> Department of Statistics / Rice University
>> http://had.co.nz/
>>
>> ______________________________________________
>> R-devel@r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
>>
>
> --
> Brian D. Ripley,                  rip...@stats.ox.ac.uk
> Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
> University of Oxford,             Tel:  +44 1865 272861 (self)
> 1 South Parks Road,                     +44 1865 272866 (PA)
> Oxford OX1 3TG, UK                Fax:  +44 1865 272595
>
> ______________________________________________
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>

______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Reply via email to