Looking at the code this seems to be based on the highly dubious assumption that no two dates produced by a recurrnce could be great than 13 months apart.
What if you recurrnce is "once every century"? I think to do recurrences that move backwards in time we have to explicitly tell the user to provide a callback that moves backwards, which would mean providing _two_ callbacks if they wanted to be able to move in both directions. Honestly, I don't think it's worth the API complication this requires. Just let the user provide one callback, and maybe specify a directory for it. Then the "next()" method can return the next date in the recurrence, which may be earlier or later than the last one returned. -dave /*======================= House Absolute Consulting www.houseabsolute.com =======================*/
