Arne said:
You have completely misunderstood the purpose of Calendar.
No, I have not. And you must stop publicly insulting me and publicly
lying about me now.
I have understood that Calendar is being used for two distinct purposes,
one of which is Locale-dependent in some way that goes beyond time
zones, and one of which is not.
Those uses should be separated into two different classes.
We are now basically quibbling over which of those to call Calendar and
which to call something else.
A pointless quibble if you ask me. Actually I'd favor keeping Calendar
similar to as-is and creating DateBuilder for basic Date-construction
jobs that don't need to care about any localization (except perhaps for
time zone matters).
It is not a formatting/parsing class.
I never claimed it was.
It is a class that applies the rules of the calendar.
Collator is a class that applies locale-dependent rules for Strings, but
you don't see Collator doing double-duty as StringBuilder.
You are telling people that computer programs should use your
calendar and not their own.
No! I am not! I am saying that the CORE of the LANGUAGE does not need to
support other than a sensible, widely-used default in this case -- more
peripheral classes or third-party ones can provide the other functionality.
I think that you are INTENTIONALLY misrepresenting what I've said as an
argument in favor of forbidding non-Gregorian calendar code ever to be
written in Java. It is not. I have never said as much. I have only
debated what should or should not be part of the core set of utility
classes.
I don't know why you keep misrepresenting me. I guess you're trying to
discredit what I say, for whatever reason. The stupid thing is, anyone
can go back to read what I actually wrote and see that you're lying your
ass off, so I don't understand why you bother to even try. It's
pointless and idiotic, and only a moron won't see right through you.
Same deal as with your deliberate misquotations earlier.
Please give it up. You are not really arguing about anything to do with
Java anymore, not as part of an honest debate and a quest for greater
understanding of Java anyway. You are just being boorish and rude out of
some sort of grudge or personal axe to grind. This is not the
appropriate venue for such behavior. Take it elsewhere.
Yes.
And BTW it is not even correct.
Yes it is.
Some types of business logic requires Calendar knowledge.
I use "business logic" to refer to the core operations only, not
whatever goes on peripherally to translate them into a user-visible
interface and to translate the user's input back in. Calendar basically
gives locale-dependent names to things like "23885436548839 milliseconds
since the epoch" and translates such back, including dates and
locale-dependent intervals and "next foobar after bazquux" type
constructs. This sort of thing is generally in the next outermost layer
of an application below the Swing/AWT using layer, along with
MessageBundle and Collator usage and lots of other Locale-related code.
Layers deeper than those top two generally shouldn't mess with Locale
save perhaps to keep track of an app-wide locale setting, store it
somewhere, and restore it.
They are not in Date - they are in Calendar.
I said "in the core Date class and its builder object"; the latter is,
at present, Calendar.
And Calendar is not a Date builder.
Yes it is. It is not SOLELY a Date builder, but it is a Date builder.
Read Date's constructors' Javadocs if you don't believe me. Most of them
are deprecated with a note pointing to Calendar. Ergo, Date construction
is generally done via Calendar instead of directly. Ergo, Calendar
functions as a Date builder.
NO. YOU ARE THE ONE WHO IS WRONG HERE, AND YOU ARE WRONG BECAUSE YOU
KEEP INTENTIONALLY MISREADING MY WORDS.
I SUGGEST A SIMPLE SOLUTION FOR THAT: STOP READING MY WORDS AT ALL.
SINCE YOU ARE APPARENTLY INCAPABLE OF REASON OR OF CIVILITY, AT LEAST
WHENEVER ADDRESSING ME, YOU SHOULD KILLFILE ME OR OTHERWISE IGNORE ME
STARTING IMMEDIATELY.
