Thanks for the clarification, Luke.
That is really counter-intuitive behavior. I 100% agree with you that the "for"
documentation should state that assumption explicitly.
I would also like to suggest changing the "for" implementation to issue a
warning if the "seq" argument is a vector of a
On Sat, 9 Mar 2013, Alexandre Sieira wrote:
Thanks for the clarification, Luke.
That is really counter-intuitive behavior. I 100% agree with you that the "for"
documentation should state that assumption explicitly.
I would also like to suggest changing the "for" implementation to issue a warn
On Mar 9, 2013, at 1:10 PM, wrote:
> R's for loop is only designed to iterato over primitive types. The
> help file says of the seq argument:
>
> seq: An expression evaluating to a vector (including a list and an
> expression) or to a pairlist or ‘NULL’. A factor value will
>
R's for loop is only designed to iterato over primitive types. The
help file says of the seq argument:
seq: An expression evaluating to a vector (including a list and an
expression) or to a pairlist or ‘NULL’. A factor value will
be coerced to a character vector.
[This
On 2013-03-09 11:14, R. Michael Weylandt wrote:
On Sat, Mar 9, 2013 at 6:50 PM, David Winsemius wrote:
I was unable to find the reason for the original coercion in the help("for")
page or the R
Language Definition entry regarding for-loops. On the hunch that coercion via
as.vector
might be oc
On Sat, Mar 9, 2013 at 6:50 PM, David Winsemius wrote:
> I was unable to find the reason for the original coercion in the help("for")
> page or the R
> Language Definition entry regarding for-loops. On the hunch that coercion via
> as.vector
> might be occurring,
Behaviorally, it seems to, but
On Mar 9, 2013, at 9:24 AM, Alexandre Sieira wrote:
> I understand that the two following loops should produce the exact same
> output. However, they do not. It appears that looping directly through the
> sequence of Date objects somehow makes them be coerced to numeric:
>
>> date1 = "20130301
7 matches
Mail list logo
