Re: [Rd] Latent flaw in SEXPREC definition

2011-08-13 Thread Radford Neal
> But the whole point of separating VECTOR_SEXPREC from the other > SEXPRECs is that they are _shorter_. A vecsxp is only going to be > larger than (say) an envsxp if 2 R_len_t's are more than 3 pointers, > which is quite unlikely since R_len_t variables holds things that > one might add to pointer

Re: [Rd] Latent flaw in SEXPREC definition

2011-08-13 Thread peter dalgaard
On Aug 13, 2011, at 22:56 , Radford Neal wrote: > There seems to be a latent flaw in the definition of struct SEXPREC > in Rinternals.h, which likely doesn't cause problems now, but could > if the relative sizes of data types changes. > > The SEXPREC structure contains a union that includes a pr

[Rd] Latent flaw in SEXPREC definition

2011-08-13 Thread Radford Neal
There seems to be a latent flaw in the definition of struct SEXPREC in Rinternals.h, which likely doesn't cause problems now, but could if the relative sizes of data types changes. The SEXPREC structure contains a union that includes a primsxp, symsxp, etc, but not a vecsxp. However, in allocVect

Re: [Rd] Rd for write.table {utils}: Be explicit about the default separator

2011-08-13 Thread Duncan Murdoch
On 11-08-13 8:01 AM, Timothy Bates wrote: In "utils/write.table.Rd" the default separator is shown as the invisible character "". In the further documentation, the default separator is not named. It would helpful to specify it using an escape character in the \Usage section "\s" or "\t"?

[Rd] Rd for write.table {utils}: Be explicit about the default separator

2011-08-13 Thread Timothy Bates
In "utils/write.table.Rd" the default separator is shown as the invisible character " ". In the further documentation, the default separator is not named. It would helpful to specify it using an escape character in the \Usage section "\s" or "\t"? and to name it explicitly in the \Arguments