Joshua Ulrich

Related to #62.

Thanks for the report! Interestingly, this also failed in 0.9-7 if the index was POSIXct, as created by `.xts`, but not as created by `xts()`. That might point to a...

This is related to #163. The fix to that bug seems to be what's triggering the error now. This is because: ```r R> storage.mode(.index(xxts)) [1] "double" R> storage.mode(.index(x.xts)) [1] "integer"...

Notes from an email discussion with the zoo team. My initial email contained the example code below: ```r x There are 3 cases we might want to handle when `i`...

Removing the milestone, since I'm not sure when (or if) this will be implemented.

Famous last words, "It seems easy enough." :) It would be great to have a horizon panel. Looking forward to the PR!

Thanks for the report! I see that you're using xts_0.11-2. Can you please try the current development version 0.12.0 and report back?

Thanks for checking! I investigated and found the cause is that `convertIndex()` doesn't actually change the underlying index values. `convertIndex()` is a simple wrapper around `` xts:::`tclass

Thanks for the report! I haven't taken a close look yet, but an (intentional) difference between xts and zoo is that the `width` argument is positive for xts and negative...

@BibeFiu can you please try the patch on the `356-rollapply-width` branch? Basically, it calls `rollapply.zoo()` any time `width` is a list. I hope that works...