On Thu, Oct 25, 2012 at 10:50 AM, Tyler Romeo <tylerromeo(a)gmail.com> wrote:
To be clear, I am not saying that any language
functionality should be in
MWTimestamp, because that's not what it's for. On the other side of it,
there should be no timestamp functionality in the Language class either. We
need a fix so that if MWTimestamp::getHumanTimestamp is called, Language is
used to generate it properly.
I disagree. The human/formatting stuff absolutely should be in Language. The
problem with having it in MWTimestamp is it requires a language or context to
be passed to do it right. This introduces a new dependency there that I don't
really like (MWTimestamp is nice and self-contained right now).
-Chad