Re: [Rd] binary string conversion to a vector (PR#14120)

2009-12-12 Thread tplate
Just responding to some of the issues in this long post: (1) Don't rely on the printed form of an object to decide whether or not they are identical. The function str() is very useful in this regard, and sometimes also unclass(). To see whether two object are identical, use the function ident

[Rd] daylight saving / time zone issues with as.POSIXlt/as.POSIXct (PR#10392)

2007-11-01 Thread tplate
Running under Windows XP 64 bit, as.POSIXlt()/as.POSIXct() seem to think that US time zones (EST5EDT, MST7MDT) switched from daylight savings back to standard time on Oct 28, 2007, whereas the switch is actually on Sun Nov 04, 2007. Examples: > Sys.timezone() [1] "Mountain Daylight Time" > as.P

[Rd] minor omissions re "special" windows file names (PR#9622)

2007-04-18 Thread tplate
"lpt1" through "lpt9" and "com1" through "com9" are in fact "special" file names under various versions of Microsoft Windows. However, "R Extensions" says only that "lpt1" through "lpt4" and "com1" through "com3" cannot be used as filenames, and "R CMD check" checks for just these filenames.

[Rd] bug in format.default: trim=TRUE does not always work as advertised (PR#9114)

2006-07-31 Thread tplate
This is a multi-part message in MIME format. --090008060607010208040805 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit DESCRIPTION OF PROBLEM: Output from format.default sometimes has whitespace around it when using big.mark="," and trim=TR

Re: [Rd] (PR#7943) documentation enhancement: Note in ?seek for Windows

2005-06-15 Thread tplate
Fair enough. But for the benefit of the unfortunate souls having to work in Windows, it would be nice if the documentation were as explicit as possible about what is and is not known about particular issues (while still being concise). How about the following: NEW: #ifdef windows The valu

[Rd] documentation enhancement: Note in ?seek for Windows (PR#7943)

2005-06-15 Thread tplate
[I started a new bug report for this issue because it was not the primary issue in the original discussion, which was PR#7899] [EMAIL PROTECTED] wrote: > Tony Plate wrote: > [snip] >>[EMAIL PROTECTED] wrote: >>[snip] >>>Note that ?seek currently tells us "The value returned by >>>seek(where