From murdoch at stats.uwo.ca  Sun Feb 22 21:25:26 2009
From: murdoch at stats.uwo.ca (Duncan Murdoch)
Date: Sun, 22 Feb 2009 15:25:26 -0500
Subject: [Rd] 'unique' error message is printed
	despite	silent=TRUE	(PR#13547)
In-Reply-To: <49A1B292.1070908@biostat.ku.dk>
References: <20090222191519.17912282C76C@mail.pubhealth.ku.dk>
	<49A1B292.1070908@biostat.ku.dk>
Message-ID: <49A1B4B6.40400@stats.uwo.ca>

On 22/02/2009 3:16 PM, Peter Dalgaard wrote:
> macrakis at alum.mit.edu wrote:
>> In 2.8.0/Windows Vista:
>>
>> When 'unique' gives a type error message, it prints out even if errors
>> are being caught:
>>
>>> try(unique(quote(hello)),silent=TRUE)
>> hello
>>
>> This comes from the .Internal unique routine:
>>
>>> try(.Internal(unique(quote(hello),NULL,NULL)),silent=TRUE)
>> hello
>>
>> I guess it is using the internal equivalent of print rather than the
>> internal equivalent of stop.
>>
> 
> silent=TRUE is a red herring (this has nothing to do with try()).
> 
> However, inside do_duplicated (unique.c) we have
> 
>      if (!isVector(x)) {
> 	PrintValue(x);
> 	error(_("%s() applies only to vectors"),
> 	      (PRIMVAL(op) == 0 ? "duplicated" : "unique"));
>      }
> 
> This is due to
> 
> ------------------------------------------------------------------------
> r32306 | ripley | 2004-12-23 22:06:27 +0100 (Thu, 23 Dec 2004) | 2 lines
> 
> Apparently unique/duplicated are supposed to work on NULL, despite their 
> help!
> 
> ...which makes little sense to explain the PrintValue(x). I suspect this 
> is a debugging printout that was inadvertently left in.

Now removed.

Duncan Murdoch



[Rd] 'unique' error message is printed despite silent=TRUE (PR#13547)
Duncan Murdoch