On Nov 24, 2011, at 1:48 PM, Prof Brian Ripley wrote:
> On Thu, 24 Nov 2011, Simon Urbanek wrote:
>
>>
>> On Nov 24, 2011, at 8:05 AM, Matthew Dowle wrote:
>>
On Nov 24, 2011, at 12:34 , Matthew Dowle wrote:
>>
>> On Nov 24, 2011, at 11:13 , Matthew Dowle wrote:
>>
On Thu, 24 Nov 2011, Simon Urbanek wrote:
On Nov 24, 2011, at 8:05 AM, Matthew Dowle wrote:
On Nov 24, 2011, at 12:34 , Matthew Dowle wrote:
On Nov 24, 2011, at 11:13 , Matthew Dowle wrote:
Hi,
I expected NAMED to be 1 in all these three cases. It is for one of
them,
but not the other
>
> On Nov 24, 2011, at 8:05 AM, Matthew Dowle wrote:
>
>>>
>>> On Nov 24, 2011, at 12:34 , Matthew Dowle wrote:
>>>
>
> On Nov 24, 2011, at 11:13 , Matthew Dowle wrote:
>
>> Hi,
>>
>> I expected NAMED to be 1 in all these three cases. It is for one of
>> them,
>> bu
The details of complex assignment expressions are fairly intricate. I
wrote up some notes ont his a couple of months back and have meant to
get them into the internals manual but have not gotten around to it
yet. I'll see if I can get to it in the next week or two and will
send a note to this th
On Nov 24, 2011, at 8:05 AM, Matthew Dowle wrote:
>>
>> On Nov 24, 2011, at 12:34 , Matthew Dowle wrote:
>>
On Nov 24, 2011, at 11:13 , Matthew Dowle wrote:
> Hi,
>
> I expected NAMED to be 1 in all these three cases. It is for one of
> them,
> but not the
>
> On Nov 24, 2011, at 14:05 , Matthew Dowle wrote:
>
>> Since list() is primitive I tried to construct a data.frame starting
>> with
>> list() [since structure() isn't primitive], but then merely adding an
>> attribute seems to set NAMED==2 too ?
>
> Yes. As soon as there is the slightest risk of
On Nov 24, 2011, at 14:05 , Matthew Dowle wrote:
> Since list() is primitive I tried to construct a data.frame starting with
> list() [since structure() isn't primitive], but then merely adding an
> attribute seems to set NAMED==2 too ?
Yes. As soon as there is the slightest risk of having (had)
>
> On Nov 24, 2011, at 12:34 , Matthew Dowle wrote:
>
>>>
>>> On Nov 24, 2011, at 11:13 , Matthew Dowle wrote:
>>>
Hi,
I expected NAMED to be 1 in all these three cases. It is for one of
them,
but not the other two?
> R --vanilla
R version 2.14.0 (2011-10-31)
On Nov 24, 2011, at 12:34 , Matthew Dowle wrote:
>>
>> On Nov 24, 2011, at 11:13 , Matthew Dowle wrote:
>>
>>> Hi,
>>>
>>> I expected NAMED to be 1 in all these three cases. It is for one of
>>> them,
>>> but not the other two?
>>>
R --vanilla
>>> R version 2.14.0 (2011-10-31)
>>> Platfo
On 11-11-24 6:34 AM, Matthew Dowle wrote:
On Nov 24, 2011, at 11:13 , Matthew Dowle wrote:
Hi,
I expected NAMED to be 1 in all these three cases. It is for one of
them,
but not the other two?
R --vanilla
R version 2.14.0 (2011-10-31)
Platform: i386-pc-mingw32/i386 (32-bit)
x = 1L
.Intern
>
> On Nov 24, 2011, at 11:13 , Matthew Dowle wrote:
>
>> Hi,
>>
>> I expected NAMED to be 1 in all these three cases. It is for one of
>> them,
>> but not the other two?
>>
>>> R --vanilla
>> R version 2.14.0 (2011-10-31)
>> Platform: i386-pc-mingw32/i386 (32-bit)
>>
>>> x = 1L
>>> .Internal(inspe
On Nov 24, 2011, at 11:13 , Matthew Dowle wrote:
> Hi,
>
> I expected NAMED to be 1 in all these three cases. It is for one of them,
> but not the other two?
>
>> R --vanilla
> R version 2.14.0 (2011-10-31)
> Platform: i386-pc-mingw32/i386 (32-bit)
>
>> x = 1L
>> .Internal(inspect(x)) # why
12 matches
Mail list logo