Joshua Ulrich

Thanks again for the detailed response! I would really appreciate it if you could send me a diff/patch of your changes that does what you suggest. That will help me...

Thanks for the report! It looks like there are multiple bugs here... You should be able to subset xts objects by selecting none of the columns. That should return a...

> ...subset xts objects by selecting none of the columns. ...but the resulting object doesn't have the correct tzone or tclass from the object that was subset. A subset that...

This change could break things. Make a test for this line in [FinancialInstrument](https://github.com/braverock/FinancialInstrument/blob/98bcf09fc80e25611897404dcd59321ef67850ac/R/redenominate.R#L211) and see if it fails. Possibly add a new field to the `periodicity()` output (e.g. `units_frequency` that...

A potential work-around: compare the 1-hour endpoints with the 30-minute endpoints. ```r R> hourEndpointsTZ30

Thanks for the report! I wouldn't say this is _inexplicable_. The column names are changed because `0` isn't a valid R object name. This behavior is consistent with `data.frame`. That...

> Now as for what `zoo` is doing, there are other inconsistencies with column naming other than this one it seems. It would be great if you could list the...

> I can start assembling that list - where would you like it to go? Add it as a comment to this issue, to start. We can decide what to...

I am closing because this is a duplicate of #114 (which is now fixed). So your examples now provide the output you expected.

Places where this behavior may affect user code: Subsetting in `[.xts` calls `isOrdered()` on `i` and/or on the output from calls to `binsearch()`. It's also called on the `INDEX` argument...