At 05:21 PM 27/07/2005, Prof Brian Ripley wrote:
>On Wed, 27 Jul 2005, Gordon Smyth wrote:
>
>>Thanks for the reply. Apologies for checking only R patched rather than
>>R-devel.
>>
>>I guess that this means that someone must have a use for
>>allowEscapes=TRUE when read reading a file in table for
On Wed, 27 Jul 2005, Gordon Smyth wrote:
> Thanks for the reply. Apologies for checking only R patched rather than
> R-devel.
>
> I guess that this means that someone must have a use for allowEscapes=TRUE
> when read reading a file in table format into a data frame. It is hard to
> imagine.
Oc
Thanks for the reply. Apologies for checking only R patched rather than
R-devel.
I guess that this means that someone must have a use for allowEscapes=TRUE
when read reading a file in table format into a data frame. It is hard to
imagine.
Gordon
At 04:59 PM 27/07/2005, Prof Brian Ripley wrote
This seems of historical interest only.
allowEscapes is currently (in R-devel, where development happens) an
argument to read.table.
We do ask people to check the current version!
On Wed, 27 Jul 2005, Gordon Smyth wrote:
>
>> To: [EMAIL PROTECTED]
>> From: Gordon Smyth <[EMAIL PROTECTED]>
>> S
>To: [EMAIL PROTECTED]
>From: Gordon Smyth <[EMAIL PROTECTED]>
>Subject: R 2.1.1: read.table processes C-style escapes
>Date: Wed, 27 Jul 2005 12:51:45 +1000
>
>In R 2.1.1, the default behaviour of scan() was changed to process all
>C-style escapes, even when a delimiter was specified using the '
In R 2.1.1, the default behaviour of scan() was changed to process all
C-style escapes, even when a delimiter was specified using the 'sep'
argument. A new argument 'allowEscapes' was introduced to turn this
processing off.
Because read.table() calls scan(), read.table() inherits the new defaul
