Deprecating haskell98 module aliases

[Neil Mitchell]

Hi,

In discussion with Gwern I've raised a bug in HLint to make using
Haskell 98 modules a warning. It's not the same as a formal
deprecation of those modules, but it's a step in that direction. I
think deprecating haskell98 modules is a reasonable step to do at some
point in the future, but I don't think that point has arrived yet (we
should at least publish Haskell 2010 first).

Thanks, Neil

2010/3/8 wren ng thornton <wren at community.haskell.org>:
> Gwern Branwen wrote:
>>
>> wren ng thornton wrote:
>>>
>>> I'm all for the warnings. And regarding guest's comments, doesn't the
>>> Haskell 2010 standard[1] count as an "actual language standard"? If not,
>>> then what is it and why isn't it one?
>>>
>>> [1] http://www.haskell.org/pipermail/haskell/2009-November/021750.html
>>
>> Correct me if I'm wrong, but I thought 'HierarchicalModules' was an
>> extension which codifies the 'Foo.Bar' import syntax (as opposed to
>> 'import FooBar'), and didn't address allocation of functions to
>> modules  or naming issues like 'Char' vs 'Data.Char' or splitting
>> 'Foreign' up or whatever.
>
> AFAIK, yes, the HierarchicalModules approval is just allowing dots in module names, rather than discussing what goes where. I was bringing haskell2010 up more to point out that the haskell98 standard is, officially, not up to date.
>
> Perhaps we should poke the haskell-prime committee to move the official location of standard functions for the haskell2011 standard?
>
> --
> Live well,
> ~wren
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://www.haskell.org/mailman/listinfo/libraries
>