RE: [boost] Re: Date-Time

I'd expect April 1st or 2nd, depending upon whether it was a leap year. I'm not sure what you're saying you'd expect.
I'd expect March 30th.
I understand what you think you want but in practice I don't think it would work out as nicely as you think now.
That would work well.
Ok, but you need more than just LAST, you need LAST-1, LAST-2, and LAST-3 That's why I use seconds..
Yes.
I would expect this as well. the 28th is either LAST, or just plain old 28th. Personally I like Jeff's solution, that you provide the increment function. Because it sounds like we have different use cases for "next month" The loose case of "see you for your next appointment next month", and "delivery is in One Month". Where 30 days is the "next month" vs the calendar end. Yours, -Gary-

From: "Powell, Gary" <powellg@amazon.com>
Why? I can't imagine a good use case for wanting one, two, or three days before the end of the month as a special form of date.
That's why I use seconds..
You still have to make them useful to humans for I/O.
Right. I took that example to mean it was the 28th day of the month of February. That is happened to be the last day of the month is irrelevant. The "LAST" or "END" form is quite separate.
Yes, but I think it is reasonable for the library to provide one or two implementations and even make one the default. If the opportunity to customize the behavior exists, you've provided for the other cases. -- Rob Stewart stewart@sig.com Software Engineer http://www.sig.com Susquehanna International Group, LLP using std::disclaimer;
participants (2)
-
Powell, Gary
-
Rob Stewart