On Tuesday 28 September 2004 7:34 am, Mario Ivankovits wrote: > Steve Cohen wrote: > >All this setting would go on as setters on a factory class that the user > > would not have to use. If they didn't setLocale, en_US would be the > > default. If they setLocale but not either date recent or older date > > format, then the standard US ordering would be used but the Locale month > > names. If they specified Locale and older date format, we could infer > > the newer date format as well. And if they specified everything, we > > could handle that case too. > > At least could you please implement this by passing in a e.g. > FTPDateObject as you stated in one of your previous mails. > > This sould have a method like > Date FTPDateObject.parse(String datepart) > or something else. > > That way one is able to pass in a completely different sort of date > parses - like the one i have in mind - which is able to automatically > determine the right month without have to set any locale (as long as the > date parts are in correct order) > > --- > Mario
If you think that I meant for the user to pass in FTPDateFormat objects, you misunderstood me. The paradigm I want to use here is passing in strings. The FTPDateFormat object was just a way of organizing thoughts. It is an object that the user would rarely if ever see. I have learned from earlier ideas of "passing in a parser" that the more complex the object you are trying to pass in, the more difficult it is for the user. For the Ant client task it is much easier to assemble the strings and construct the needed objects ourselves, than it is to make the user do it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
