#1231: deprecation warnings are reported too often
----------------------------------------------+-----------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: feature request | Status: new
Priority: low | Milestone: 6.8
Component: Compiler | Version: 6.6
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Os: Multiple | Testcase:
nhc98/src/compiler98
Architecture: Multiple |
----------------------------------------------+-----------------------------
Comment (by [EMAIL PROTECTED]):
SimonPJ asked:
Since you are the one who tripped over this, would you like to draft
some new text for the user manual, that
describes precisely when a deprecation warning is emitted? Then I'll
implement it. Start with the text here:
http://www.haskell.org/ghc/docs/latest/html/users_guide/pragmas.html
#deprecated-pragma
My suggestion is to change the penultimate paragraph which currently
reads:
Any use of the deprecated item, or of anything from a deprecated module,
will be flagged with an appropriate message.
However, deprecations are not reported for (a) uses of a deprecated
function within its defining module, and (b) uses of
a deprecated function in an export list. The latter reduces spurious
complaints within a library in which one module
gathers together and re-exports the exports of several others.
to
Any use of the deprecated item, or of anything from a deprecated module,
will be flagged with an appropriate message.
However, deprecations are not reported for uses of a deprecated entity
(a) within its defining module, (b) within an export
list, or (c) in a module that imports the entity from another module in
the same package, but where the entity was
originally defined in a different package. Conditions (b) and (c) reduce
spurious complaints within a library in which
one module gathers together and re-exports the exports of several
others.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1231>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
