Luke Tierney <[EMAIL PROTECTED]> wrote:
> I am not comfortable making this available at this point. It might be
> useful to have but would need careful thought. Without some way to
> find out the true length there are potential problems. Without some
> way of making sure the fields in VECSXP an
On Mon, 5 Sep 2005, [EMAIL PROTECTED] wrote:
> Luke Tierney <[EMAIL PROTECTED]> wrote:
>
>> It might or might not work now but is not guaranteed to do so reliably
>> in the future. Seeing the risks of leaving SETLENGTH exposed, it is
>> very likely that SETLENGTH will be removed from the sources
Luke Tierney <[EMAIL PROTECTED]> wrote:
> It might or might not work now but is not guaranteed to do so reliably
> in the future. Seeing the risks of leaving SETLENGTH exposed, it is
> very likely that SETLENGTH will be removed from the sources after the
> 2.2.0 release.
> If you provide your ow
On Mon, 5 Sep 2005, [EMAIL PROTECTED] wrote:
> Luke Tierney <[EMAIL PROTECTED]> wrote:
>
>> This is not supported by the memory manager. Using SETLENGTH to
>> change the length would confuse the garbage collector--we should
>> probably remove SETLENGTH from the headers.
>
>> The memory manager do
On Sun, 4 Sep 2005, [EMAIL PROTECTED] wrote:
> Can someone explain the use of SETLENGTH() and SETTRUELENGTH()?
>
> I would like to allocate a vector and reserve some space at the end,
> so that it appears shorter than the allocated size. So that I can
> more efficiently append to the vector, wit
Can someone explain the use of SETLENGTH() and SETTRUELENGTH()?
I would like to allocate a vector and reserve some space at the end,
so that it appears shorter than the allocated size. So that I can
more efficiently append to the vector, without requiring a new copy
every time. So I'd like to use
