Cron Format not the same as Cron Spec

[bryanvpham]

Out of all the libraries and sites I've seen everybody who uses the six * supports year instead of seconds.
For Example:
http://www.nncron.ru/help/EN/working/cron-format.htm

I personally think it would be better to follow what everyone else is doing to avoid confusion. It also lets it work with libraries that convert cron strings into human-readable format.

I don't think running a function every second is very good use case nor is running functions at specific second intervals. Might as well just use "sleep" or tickers. Years probably won't be that useful either but having a more compatible format would be nice.

[soltysh]

@robfig I'd like to expose a 2nd method to comply what was stated here, so that you're able to provide the usual 6 fields, are you ok with me doing so? It won't happen sooner than beginning of September when I'm back from PTO.

[robfig]

Yeah, I agree. I wrote it so long ago now that I have no idea why I would have done seconds instead of years -- I thought I just implemented it according to the wikipedia Cron page, but that doesn't have seconds either. Maybe I was using the Quartz format instead. Adding a second method seems like the right way to handle it to avoid breaking existing users.
Thank you!

[saraswat40]

Can someone provide an example of how this will be used? The current documentation assumes that a 5 option string will be passed. Is the 6 option string handled implicitly? Is it possible to update the documentation to include a 6 option example? I am trying to create a parser which would support cron jobs to run say every other year