old-locale

[Brandon Allbery]

On Mon, Oct 24, 2011 at 14:08, Jason Dagit <dagitj at gmail.com> wrote:

> On Mon, Oct 24, 2011 at 12:53 AM, Ashley Yakeley <ashley at semantic.org>
> wrote:
> > On Sun, 2011-10-23 at 06:11 +0200, Michael Snoyman wrote:
> >> Perhaps this belongs in a separate discussion, but is there any plan
> >> to have time provide the locale stuff directly instead of our code
> >> needing to depend on old-locale? If I'm not mistaken, implementing
> >> such a strategy at the same time would mean that user code could then
> >> ignore two old-* packages.
> >
> > No, locale is not part of time. Nor am I interested in taking
> > responsibility for it.
> >
> > According to  http://www.haskell.org/haskellwiki/Library_submissions ,
> > old-locale is "maintained only for backward compatibility". And yet
> > no-one can tell me where any new "locale" package is or why the old
> > "locale" became "old-locale" or what might count as "forward"
> > compatibility. Nor do I know of any particular problems with it, but
> > then I haven't examined its subject area particularly closely.
>
> I've tripped on this as well.  Putting 'old-foo' in a cabal file feels
> wrong, but when I looked I also couldn't find any discussion as to why
> it is called old-locale.


My understanding is [old-]locale was used only by [old-]time; it was
intended to gather various locale dependent things, but never did.  So when
time was deprecated to old-time, locale went along with its only consumer.

-- 
brandon s allbery                                      allbery.b at gmail.com
wandering unix systems administrator (available)     (412) 475-9364 vm/sms
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20111024/a29fc684/attachment.htm>