From wdunlap at tibco.com  Thu Nov  6 02:05:26 2008
From: wdunlap at tibco.com (William Dunlap)
Date: Wed, 5 Nov 2008 17:05:26 -0800
Subject: [Rd] puzzled by cat() behaviour when argument '...' is a
	vector(and argument 'sep' contains "\n")
In-Reply-To: <77EB52C6DD32BA4D87471DCD70C8D7001DE739@NA-PA-VBE03.na.tibco.com>
References: <49122279.3080203@web.de> <491231BF.6030007@stats.uwo.ca>
	<77EB52C6DD32BA4D87471DCD70C8D7001DE739@NA-PA-VBE03.na.tibco.com>
Message-ID: <77EB52C6DD32BA4D87471DCD70C8D7001DE74D@NA-PA-VBE03.na.tibco.com>

> -----Original Message-----
> From: r-devel-bounces at r-project.org 
> [mailto:r-devel-bounces at r-project.org] On Behalf Of William Dunlap
> Sent: Wednesday, November 05, 2008 4:51 PM
> To: Duncan Murdoch; Peter Ruckdeschel
> Cc: r-devel at r-project.org
> Subject: Re: [Rd] puzzled by cat() behaviour when argument 
> '...' is a vector(and argument 'sep' contains "\n")
...
> Neither use any entry in sep after the end of the cat() 
> output, although, because of the previous rule, it may seem 
> that they do in the common case of sep="".

I meant 'common case of sep="\n"'.
 
> I had forgotten that sep= could be vectorized and use paste() 
> instead of
> cat() when I needed such functionality.  IMO, paste() has 
> fewer surprises.
> 
> Bill Dunlap
> TIBCO Spotfire Inc
> wdunlap tibco.com 



[Rd] puzzled by cat() behaviour when argument '...' is a vector(and argument 'sep' contains "\n")
William Dunlap