From spinuvit.list at gmail.com  Fri Aug 20 00:02:05 2010
From: spinuvit.list at gmail.com (Vitaly S.)
Date: Fri, 20 Aug 2010 00:02:05 +0200
Subject: [Rd] c.POSIXct
References: <AANLkTinGcXRQd5+Xmo2ad5HoofdbzhZbEaSznAgCL3vO@mail.gmail.com>
	<AANLkTin=8k4UfBqzjQmHa9ntQP3V9zhuhsfkL_qzZyWi@mail.gmail.com>
	<257F72DF-1C81-439A-8893-76B793C9820C@r-project.org>
	<AANLkTi=wd0jcTUhpAJpofxUJy5fB3apLKq8704DV6k6q@mail.gmail.com>
	<4C6CB10C.3000204@structuremonitoring.com>
Message-ID: <878w429s82.fsf@gmail.com>

Spencer Graves <spencer.graves at structuremonitoring.com> writes:

>        I'm with Gabor on this.  I naively would not expect c() to strip attributes generally, and I've been
> surprise more than once to find the time zone attribute stripped when I did not expect that.
>
>
>       Might it make sense to add an argument like "keepAttributes=FALSE" to the "c" function?  Then people like
> Gabor and me would know that we would have to specify "keepAttributes = TRUE" if we wanted attributes to be kept.

I often find myself using c() just to strip attributes when manipulating arrays
in simulation. c() is probably already quite complex function,
"keepAttributes=FALSE" would complicate it even more and impact the speed.

Given that, I wonder why there is no dedicated function to strip attributes.
Am I missing anything?

Vitaly.



[Rd] c.POSIXct
Vitaly S.