Although apparantly simple, all date methods and concepts get complex very quickly. For example timezone handling and daylight savings handling. These methods don't feel like the right additions to DateUtils at the moment.
Stephen ----- Original Message ----- From: "Ash .." <[EMAIL PROTECTED]> > The following date generators in the o.a.c.l.t.Dateutils class might be > useful. Requesting feedback. > > public static Calendar getCalendarXxxAgo(int value) > public static Date getDateXxxAgo(int value) > > Xxx = weeks, days, months, years, ... > > E.g., > Calendar jobJoinDate = DateUtils.getCalendarYearsAgo(10); > > Likewise, > > public static Calendar getCalendarXxxHence(int value) > public static Date getDateXxxHence(int value) > > Calendar taskProcrastinationPeriod = Calendar.getCalendarDaysHence(3); > > Further, the special cases of value == 1, may be provided as special > methods: > > getLastMonth(), getNextMonth(), etc. > > Request feedback. I might want to implement this, thow getDateDaysHence(val) > val could be high > ;-) > > Ash > > > > > > > > > --------------------------------------------- > > Run, rabbit run. > Dig that hole, forget the sun, > And when at last the work is done > Don't sit down it's time to dig another one. > > _________________________________________________________________ > Get Hotmail on your mobile phone http://www.msn.co.uk/msnmobile > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
