You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
(64) |
May
(62) |
Jun
(33) |
Jul
(61) |
Aug
(75) |
Sep
(61) |
Oct
(124) |
Nov
(18) |
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(42) |
Feb
(19) |
Mar
(12) |
Apr
(34) |
May
(10) |
Jun
(4) |
Jul
(23) |
Aug
(24) |
Sep
(12) |
Oct
(48) |
Nov
(36) |
Dec
(48) |
2004 |
Jan
(26) |
Feb
(19) |
Mar
(21) |
Apr
(14) |
May
(9) |
Jun
(19) |
Jul
(44) |
Aug
(46) |
Sep
(27) |
Oct
(23) |
Nov
(30) |
Dec
(46) |
2005 |
Jan
(17) |
Feb
(36) |
Mar
(31) |
Apr
(53) |
May
(27) |
Jun
(20) |
Jul
(17) |
Aug
(48) |
Sep
(88) |
Oct
(55) |
Nov
(20) |
Dec
(50) |
2006 |
Jan
(36) |
Feb
(59) |
Mar
(39) |
Apr
(14) |
May
(19) |
Jun
(26) |
Jul
(54) |
Aug
(50) |
Sep
(19) |
Oct
(19) |
Nov
(37) |
Dec
(25) |
2007 |
Jan
(31) |
Feb
(33) |
Mar
(16) |
Apr
(9) |
May
(20) |
Jun
(30) |
Jul
(6) |
Aug
(48) |
Sep
(8) |
Oct
(20) |
Nov
(15) |
Dec
(21) |
2008 |
Jan
(49) |
Feb
(12) |
Mar
(31) |
Apr
(10) |
May
(25) |
Jun
(23) |
Jul
(22) |
Aug
(15) |
Sep
(27) |
Oct
(27) |
Nov
(28) |
Dec
(20) |
2009 |
Jan
(14) |
Feb
(7) |
Mar
(34) |
Apr
(10) |
May
(14) |
Jun
(2) |
Jul
(25) |
Aug
(8) |
Sep
(14) |
Oct
(17) |
Nov
(7) |
Dec
(15) |
2010 |
Jan
(4) |
Feb
(35) |
Mar
(21) |
Apr
(31) |
May
(1) |
Jun
(13) |
Jul
(28) |
Aug
(14) |
Sep
(19) |
Oct
(6) |
Nov
(15) |
Dec
(15) |
2011 |
Jan
(29) |
Feb
(12) |
Mar
(8) |
Apr
(21) |
May
(40) |
Jun
(12) |
Jul
(24) |
Aug
(19) |
Sep
(29) |
Oct
(21) |
Nov
(18) |
Dec
(30) |
2012 |
Jan
(10) |
Feb
(18) |
Mar
(19) |
Apr
(16) |
May
(15) |
Jun
(12) |
Jul
(9) |
Aug
(3) |
Sep
(16) |
Oct
(11) |
Nov
(8) |
Dec
|
2013 |
Jan
(5) |
Feb
(1) |
Mar
|
Apr
|
May
(7) |
Jun
(8) |
Jul
(20) |
Aug
(11) |
Sep
(6) |
Oct
|
Nov
(1) |
Dec
|
2014 |
Jan
(5) |
Feb
(3) |
Mar
|
Apr
|
May
(2) |
Jun
(2) |
Jul
|
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(1) |
2017 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Guy A. <ga...@pe...> - 2002-04-15 18:21:05
|
Hi all - Initial commit's done about 15 minutes ago. Take a look, let me know what you think please. Regards, Guy |
From: Guy A. <gal...@ly...> - 2002-04-14 22:39:40
|
Stephen - I am about ready to add: org/joda/time/DateTimeComparator.java org/joda/test/time/TestDateTimeComparator.java Any considerations vis-a-vis Unix vs. Windows line ends? Regards, Guy See Dave Matthews Band live or win a signed guitar http://r.lycos.com/r/bmgfly_mail_dmb/http://win.ipromotions.com/lycos_020201/splash.asp |
From: Stephen C. <ste...@ho...> - 2002-04-14 21:15:43
|
> I was thinking that: > > DateTime( -1000 ); > > and > > DateTime("1969-12-31T23:59:59"); > > were equivalent. Is that not the case? No, currently the DateTime class does not know about timezones, thus everything is always created in GMT. The string parser is based on SimpleDateFormat which is based on Date which DOES know about timezones. Thus a horrible mess ensues :-( Kandarp raised this problem a little while back and was going to take a look. Basically, some rework in DateTime is essential. Currently problems with that class are affecting the TimePeriod and Comparator work. The two choices are 1) Make DateTime timezone aware - which makes the class much more complex 2) Keep DateTime as GMT only, and fix the String parser I think we shall have to do 1, but it causes various problems (timezone includes daylight savings as well, but ISO8601 doesn't) Stephen |
From: Guy A. <gal...@ly...> - 2002-04-14 19:45:54
|
Hi all - I am going slightly crazy trying to get the Hour/Minute/Second code in DateTimeComparator tested to my satisfaction. Let's just look at 'hour' for now. Consider this code: <code> import java.util.* ; import java.text.* ; import org.joda.time.* ; import org.joda.util.* ; public class hourTesta { public static void main(String[] args) { new hourTesta().go(); } private void go() { String end69as = "1969-12-31T23:59:59"; String start70as = "1970-01-01T00:00:00"; DateTime dt69a = null; DateTime dt70a = null; try { dt69a = new DateTime( end69as ); dt70a = new DateTime( start70as ); } catch(ParseException pe) { pe.printStackTrace(); System.exit(1); } DateTime dt69b = new DateTime(-1000); // 1s=1000ms DateTime dt70b = new DateTime(0); showDT(dt69a, "dt69a"); showDT(dt70a, "dt70a"); showDT(dt69b, "dt69b"); showDT(dt70b, "dt70b"); } private void showDT(DateTime zzz, String vn) { System.out.println("============ " + vn); System.out.println("DateTime = " + zzz); System.out.println("long Value = " + zzz.getMillis() ); System.out.println("HourOfDay = " + zzz.getHourOfDay() ); return; } } </code> I normally run (Linux box) with TZ=EST5EDT. Here is log of output with two tests, one TZ=EST5EDT, and one TZ=GMT. <testlog> ++ export TZ=EST5EDT ++ TZ=EST5EDT ++ java hourTesta ============ dt69a DateTime = 1969-12-31T23:59:59 long Value = 17999000 HourOfDay = 4 ============ dt70a DateTime = 1970-01-01T00:00:00 long Value = 18000000 HourOfDay = 5 ============ dt69b DateTime = 1969-12-31T18:59:59 long Value = -1000 HourOfDay = 0 ============ dt70b DateTime = 1969-12-31T19:00:00 long Value = 0 HourOfDay = 0 ++ export TZ=GMT ++ TZ=GMT ++ java hourTesta ============ dt69a DateTime = 1969-12-31T23:59:59 long Value = -1000 HourOfDay = 0 ============ dt70a DateTime = 1970-01-01T00:00:00 long Value = 0 HourOfDay = 0 ============ dt69b DateTime = 1969-12-31T23:59:59 long Value = -1000 HourOfDay = 0 ============ dt70b DateTime = 1970-01-01T00:00:00 long Value = 0 HourOfDay = 0 ++ set +x </testlog> There are eight (8) tests in the above code. I do not understand why: Hour of day appears incorrect in tests: 1, 2, 3, 5, 7 I also do not understand the output of some of the implicit invocations of DateTime.toString(). I was thinking that: DateTime( -1000 ); and DateTime("1969-12-31T23:59:59"); were equivalent. Is that not the case? Regards, Guy See Dave Matthews Band live or win a signed guitar http://r.lycos.com/r/bmgfly_mail_dmb/http://win.ipromotions.com/lycos_020201/splash.asp |
From: Stephen C. <ste...@ho...> - 2002-04-14 10:15:12
|
I've just taken a quick look. Looks good. Here are a few things I spotted: 1) StartDate and EndDate in TimePeriod are currently held as ReadableDateTime objects, and the get methods return them as such. I think that they should probably be held as DateTime period objects internally and returned as such. The constructor would still take in a ReadableDateTime but create a new DateTime from the value. This change would limit our exposure to other (possibly broken) implementations of DateTime and generally fits with how I envisaged the interfaces being used (input parameters are interfaces, return values are classes). 2) Thinking about it some more, the constructors should take in a ReadableInstant not a ReadableDateTime, and a ReadablePeriod not a ReadableTimePeriod. The more generic the input the better. 3) In the formatter, 'omit' only has one 'm' ;-) Let me know what you make of these suggestions. Good work though. Stephen BTW: For testing, JUnit is in use (to some degree) See JodaUtils/test/org/joda/time/TestDateTime for an example > Hi all. > > Ive put my initial implementation of the TimePeriod and > TimePeriodFormat classes on the CVS. They arent complete and I havent > tested them yet, but I thought someone might like to see how they are > going nonetheless. > > Regards > _____________________ > Sean Geoghegan |
From: Sean G. <sge...@bi...> - 2002-04-14 08:52:51
|
Hi all. Ive put my initial implementation of the TimePeriod and TimePeriodFormat classes on the CVS. They arent complete and I havent tested them yet, but I thought someone might like to see how they are going nonetheless. Regards _____________________ Sean Geoghegan sge...@bi... |
From: Stephen C. <ste...@ho...> - 2002-04-13 13:06:37
|
> So should we define clone in the > ReadableInstant interface or something similar? Yes, I have done this for ReadableInstant and ReadablePeriod on CVS Stephen |
From: Stephen C. <ste...@ho...> - 2002-04-13 12:57:40
|
> >In the book 'Effective Java' by Joshua Bloch it details various good > >programming practices. > > This as good as Scott Meyers' Effective C++? I'll check it out. A lot of it is common sense, but I'll guarantee you'll find something you didn't know. Definitely worthwhile to have. The format is borrowed from the Scott Meyer book (I haven't read that, so I can't compare directly). |
From: Sean G. <sge...@bi...> - 2002-04-13 05:16:03
|
Hi all. I am getting the following errors when trying to clone a DateTime object when it has been cast to a ReadableDateTime. I suspect it is because the clone method isnt actually defined in any of the interfaces that DateTime implements which mean the clone call falls back onto the clone method defined in Object which is protected. So should we define clone in the ReadableInstant interface or something similar? Sean org/joda/time/TimePeriod.java [108:1] protected native Object clone() throws java.lang.CloneNotSupportedException has protected access in org.joda.time.ReadableDateTime startDate = (ReadableDateTime)start.clone(); ^ org/joda/time/TimePeriod.java [109:1] protected native Object clone() throws java.lang.CloneNotSupportedException has protected access in org.joda.time.ReadableDateTime endDate = (ReadableDateTime)end.clone(); ^ org/joda/time/TimePeriod.java [124:1] protected native Object clone() throws java.lang.CloneNotSupportedException has protected access in org.joda.time.ReadableDateTime startDate = (ReadableDateTime)start.clone(); ^ org/joda/time/TimePeriod.java [141:1] protected native Object clone() throws java.lang.CloneNotSupportedException has protected access in org.joda.time.ReadableDateTime endDate = (ReadableDateTime)end.clone(); ^ 4 errors Errors compiling TimePeriod [Local]. _____________________ Sean Geoghegan sge...@bi... |
From: Stephen C. <ste...@ho...> - 2002-04-12 20:09:08
|
> The invocation of the private constructor as shown above implies that we really need to write: > public class DateTimeComparator > implements Comparator { Correct > Up to this point I have not overridden 'equals', merely passing the buck to java.lang.Object. > > After thinking a little about 'equals', I initially conclude that: it does not really make sense to override 'equals' in the context of the DateTimeComparator class. Yes, no implementation of equals/hashcode is required. > When 'equals' is invoked on a DateTimeComparator object: > > 'this' is a DateTimeComparator > (java.util.Comparator) > > 'that' would be a ?. Presumably one of the supported object types (DateTime, ReadableInstant, ......). In the book 'Effective Java' by Joshua Bloch it details various good programming practices. One is how to write a good equals method (it turns out to be quite tough). Basically, the equals method cannot make reference to other object types such as DateTime and ReadableInstant, beacuase they do not make reference to DateTimeComparators in their equals methods. Since DateTimeComparator objects can only be created by the private constructor, the == test is sufficient for comparing the comparator objects. (ie. equals compares the comparator objects, not the year/month part of the date) To compare if two dates have the same month you can write if (MONTH_COMPARATOR.compare(dateTime1, dateTime2) == 0) { // same month } Thus, the compare method is the only one that needs writing really. We could provide a convenience method for this on DateTimeComparator, but I don't think it's necesssary. It will be easy enough to add later if we get requested for it. Stephen |
From: Guy A. <gal...@ly...> - 2002-04-12 16:17:26
|
Hi Stephen and all - A portion of your code fragment showing an outline of DateTimeComparator is shown here: <code> public class DateTimeComparator { .... public static final Comparator MONTH_COMPARATOR = new DateTimeComparator(int[] {MONTH_OF_YEAR}); .... } </code> The invocation of the private constructor as shown above implies that we really need to write: <code> public class DateTimeComparator implements Comparator { .... </code> OK so far, I have done that. Somewhat arbitrarily I started this by coding of the interface specified 'compare' method. I have this working fairly well. Your idea of the 'array of integers' works well in practice. (There *are* additional problems with some of the DateTime.getXXX methods - I will document these in another email later today or tomorrow). Up to this point I have not overridden 'equals', merely passing the buck to java.lang.Object. After thinking a little about 'equals', I initially conclude that: it does not really make sense to override 'equals' in the context of the DateTimeComparator class. When 'equals' is invoked on a DateTimeComparator object: 'this' is a DateTimeComparator (java.util.Comparator) 'that' would be a ?. Presumably one of the supported object types (DateTime, ReadableInstant, ......). This leads me to ask myself other questions: -Is this really a 'Comparator'? -Might 'compare' not be better implemented as a convenience method somwhere else, say DateTimeUtils?(I think this causes other problems) -What if we did not implement Comparator, and just returned a DateTimeComparator? In that case, I don't like the class name. Asking for your thoughts and guidance please. Regards, Guy See Dave Matthews Band live or win a signed guitar http://r.lycos.com/r/bmgfly_mail_dmb/http://win.ipromotions.com/lycos_020201/splash.asp |
From: Stephen C. <ste...@ho...> - 2002-04-11 23:40:36
|
Guy, You are correct. Year was returning the correct year only after 1900. I have corrected Year, MonthOfYear and DayOfMonth and these now return the same results as GregorianCalendar for 1583-10000. See CVS for DateTime and DateTimeUtils. Stephen > Hi all - I am trying to confirm/deny one/more bugs in DateTime (uncovered in testing of DateTimeComparator). > > Please try this code, and see if the year 1900 is output (as in my test here). > > <code> > String sdt = "1899-12-31T00:00:00"; > DateTime dt = null; > try { > dt = new DateTime( sdt ); > } catch(ParseException pe) { > pe.printStackTrace(); > System.exit(1); > } > System.out.println("DateTime is: " + dt); > System.out.println("Year is: " + dt.getYear() ); > </code> > > I also see other discrepancies in DateTime getXXXX methods, but think (am sure) some of them follow from occaisional incorrect calculations of 'year'. > > Regards, Guy > > > > > See Dave Matthews Band live or win a signed guitar > http://r.lycos.com/r/bmgfly_mail_dmb/http://win.ipromotions.com/lycos_020201 /splash.asp > > _______________________________________________ > Joda-interest mailing list > Jod...@li... > https://lists.sourceforge.net/lists/listinfo/joda-interest > |
From: Guy A. <gal...@ly...> - 2002-04-11 21:44:48
|
Hi all - I am trying to confirm/deny one/more bugs in DateTime (uncovered in testing of DateTimeComparator). Please try this code, and see if the year 1900 is output (as in my test here). <code> String sdt = "1899-12-31T00:00:00"; DateTime dt = null; try { dt = new DateTime( sdt ); } catch(ParseException pe) { pe.printStackTrace(); System.exit(1); } System.out.println("DateTime is: " + dt); System.out.println("Year is: " + dt.getYear() ); </code> I also see other discrepancies in DateTime getXXXX methods, but think (am sure) some of them follow from occaisional incorrect calculations of 'year'. Regards, Guy See Dave Matthews Band live or win a signed guitar http://r.lycos.com/r/bmgfly_mail_dmb/http://win.ipromotions.com/lycos_020201/splash.asp |
From: Stephen C. <ste...@ho...> - 2002-04-11 09:26:28
|
Guy, What I had in mind was the ability for people to have a comparator that compared the date part ignoring the time. In other words it would compare the years, and if they were equal it would compare the month, and if they were equal it would compare the day. In my pseudo code I achieved this using an int[] that specifies the fields to compare, and the order - you can choose to do this in whatever way best fits the rest of your code. Bear in mind however that we will at least want a TIME_COMPARATOR that compares the three time fields in order as well (hour then minute then second). Plus we will probably end up adding other combinations. The int[] specifying a list of comparisons to do in order seemed like a flexible reusable design to allow this without too much cut and paste (just loop around the array until you get a result != 0) Hope this helps Stephen >Hi - This is primarily a question for Stephen. > >Part of one of your previous explanations included this line of code as >part of an example: > >public static final Comparator DATE_COMPARATOR = > new int[] {YEAR, MONTH_OF_YEAR, DAY_OF_MONTH}); > >For the above case (DATE), would not an array with only one unique constant >suffice? > >What additional semantics are implied by an array with more than one >element? (fields.length > 1) > >I thought I had a pretty good handle on this (even have some working code) >until I went back and saw that. > >Regards, Guy _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. |
From: Guy A. <gal...@ly...> - 2002-04-11 00:37:07
|
Hi - This is primarily a question for Stephen. Part of one of your previous explanations included this line of code as part of an example: public static final Comparator DATE_COMPARATOR = new int[] {YEAR, MONTH_OF_YEAR, DAY_OF_MONTH}); For the above case (DATE), would not an array with only one unique constant suffice? What additional semantics are implied by an array with more than one element? (fields.length > 1) I thought I had a pretty good handle on this (even have some working code) until I went back and saw that. Regards, Guy See Dave Matthews Band live or win a signed guitar http://r.lycos.com/r/bmgfly_mail_dmb/http://win.ipromotions.com/lycos_020201/splash.asp |
From: Guy A. <gal...@ly...> - 2002-04-11 00:22:50
|
Hi all - If I uncover bugs in other parts of the code while I am working on a particular assignment should I: -Post here first for discussion -Just add to the bug tracking system (Do I have authority to do that?) -Other? Thanks, Guy See Dave Matthews Band live or win a signed guitar http://r.lycos.com/r/bmgfly_mail_dmb/http://win.ipromotions.com/lycos_020201/splash.asp |
From: Guy A. <gal...@ly...> - 2002-04-10 14:59:52
|
Hi all - Here is a copy of the e-mails between Stephen and myself to date regarding Joda feature request number 534049. Now that I have access to this mailing list, I will use it in future for any questions / discussions. Regards, Guy ================================================================== Guy, I will add you to the project. A client of the comparator API would use it as follows: DateTime a = new DateTime("2007-04-20T00:00:00"); DateTime b = new DateTime("2002-05-20T00:00:00"); DateTime c = new DateTime("2002-01-20T00:00:00"); List list = new ArrayList(); list.add(a); list.add(b); list.add(c); Collections.sort(list); ...sorts them in the order (c,b,a) as the default order takes into account all the fields. Collections.sort(list, DateTimeComparators.YEAR); ...sorts them in the order (b,c,a) or (c,b,a) based only on the year. Collections.sort(list, DateTimeComparator.MONTH); ...sorts them in the order (c,a,b) which is the order of the month field. I hope this make it clearer. See also http://java.sun.com/docs/books/tutorial/collections/index.html in particular the algorithms section. Thanks Stephen _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx ================================================================ Guy, Thanks for looking at this. What I am looking for is slightly different to what you describe. It involves creating instances of the java.util.Comparator interface in a new class, DateTimeComparator. It has a number of static final constant Comparator instances. Each comparator instance is for some part of the datetime that could be compared: public class DateTimeComparator { public static final Comparator YEAR_COMPARATOR = new DateTimeComparator(new int[] {YEAR}); public static final Comparator MONTH_COMPARATOR = new DateTimeComparator(new int[] {MONTH_OF_YEAR}); public static final Comparator DATE_COMPARATOR = new DateTimeComparator(new int[] {YEAR, MONTH_OF_YEAR, DAY_OF_MONTH}); ... private static int YEAR = 0; ... private DateTimeComparator(int[] fields) { ... } ... } One comparator would be created for each of the 11 fields you identified. Plus there would need to be comparators for Date (year, month, day) and Time (Hour, Minutes, Seconds, Millis). This is why I suggest using some kind of int constants to pass into a constructor, so if we want to create other combinations of fields to compare on in the future its easy. One final thing, the compare(Object, Object) method needs to be able to compare instances of ReadableInstant, java.util.Date, Long (millisecs) and java.util.Calendar (for maximum flexibility). This will involve extracting the number of milliseconds from each to convert to DateTime objects for the comparision. I hope that this is OK. Let me know if you have any questions, or have any better ideas on the design. (In case you were wondering, I am trying to keep the DateTime API itself fairly small, which is why I want to create a separate class for this.) Thanks Stephen PS. Let me know you sourceforge username, and I can add you to the project. PPS. There is a low volume mailing list available from the joda sourceforge project page which any discussions should probably be held on. > Hi Stephen - I got a CVS snapshot this morning via anonymous checkout, got a > clean build, and started to look at code based on your previous e-mail. > > Let me describe what you are asking for, and then you tell me where I'm off > :-). > > Modifications to: > > org.joda.time.DateTime > org.joda.test.time.TestDateTime > > Relevant accessors in DateTime are: > > MillisOfSecond > SecondOfMinute > MinuteOfHour > HourOfDay > DayOfWeek > DayOfMonth > DayOfYear > WeekOfYearWeek > WeekOfYearYear > MonthOfYear > Year > > All accessors return int's. > > For each of these accessors, add the following methods to DateTime: > > compare*To > is*After > is*Before > > Each of these methods to be overloaded once, first with an 'int' > parameter, second with a 'DateTime' parameter. > > Example method signatures for MillisOfSecond: > > public int compareMillisOfSecondTo(int) > public int compareMillisOfSecondTo(DateTime) > public boolean isMillisOfSecondBefore(int) > public boolean isMillisOfSecondBefore(DateTime) > public boolean isMillisOfSecondAfter(int) > public boolean isMillisOfSecondAfter(DateTime) > > Add test methods to TestDateTime for each of the above new methods > in DateTime. (I'm not really familiar with junit, but will do > some reading). > > Please let me know what you think. > > Regards, Guy Allard See Dave Matthews Band live or win a signed guitar http://r.lycos.com/r/bmgfly_mail_dmb/http://win.ipromotions.com/lycos_020201/splash.asp |
From: Guy A. <gal...@ly...> - 2002-04-10 01:57:53
|
Hi guys - If you get this, I apologize for the spam. Just trying to make sure my link to this list works. Regards, Guy See Dave Matthews Band live or win a signed guitar http://r.lycos.com/r/bmgfly_mail_dmb/http://win.ipromotions.com/lycos_020201/splash.asp |
From: Stephen C. <sco...@eu...> - 2002-04-07 22:00:14
|
I have removed the marker interfaces from org.joda.util Readable Writeable Unmodifiable Immutable They didn't do anything useful, and did increase the dependencies between packages. (At some stage we may need org.joda.time to be a standalone package). This impacted certain classes in the org.joda.time package. Stephen |
From: Stephen C. <sco...@eu...> - 2002-04-03 20:45:53
|
Sean, I was thinking about the list of constructors on the TimePeriod class. There should probably be one more - TimePeriod(ReadablePeriod) This would allow a TimePeriod to be constructed from some other implementation of the interface, or another TimePeriod. Does this sound sensible? Stephen PS. Joda now has this mailing list jod...@li.... I took the liberty of signing you up. Discussions about Joda that are non-personal should go through the mailing list now, so we keep a record of decisions for future history. You should have received unsubscribe instructions already should you wish to use them in the future. |