#3303: Allow multi-line deprecation messages.
---------------------------------+------------------------------------------
    Reporter:  duncan            |        Owner:                  
        Type:  bug               |       Status:  new             
    Priority:  normal            |    Milestone:                  
   Component:  Compiler          |      Version:  6.10.2          
    Severity:  normal            |   Resolution:                  
    Keywords:                    |   Difficulty:  Unknown         
    Testcase:                    |           Os:  Unknown/Multiple
Architecture:  Unknown/Multiple  |  
---------------------------------+------------------------------------------
Changes (by simonpj):

  * difficulty:  => Unknown

Comment:

 Concerning line wrapping, it's not clear that you want GHC to re-wrap your
 text at arbitrary places.  You might care where the line breaks are.  How
 about this: instead of giving one string, you can instead give a list of
 strings, which are displayed on successive lines.  So input is:
 {{{
 {-# DEPRECATED defaultUserHooks
      ["Use simpleUserHooks or autoconfUserHooks, unless you need
 Cabal-1.2"
      , "compatibility in which case you must stick with defaultUserHooks"]
   #-}
 }}}
 The output would look as you'd expect.  This is nice because it's backward
 compatible, and deals with points from the original report.

 Concerning constructors vs types, the very same thing comes up with fixity
 declarations, at least when you use GHC's ability to have infix type
 constructors:
 {{{
   infix 4 :+:
 }}}
 I'd be happy with a disambiguating prefix `constructor`, `type`, or
 `class`; at least when there ''was'' ambiguity.  That means making
 `constructor` a new `special_id`, but it wouldn't be a keyword except in
 these two special situations, like other `special_id`s.

 Comments?

 Simon

-- 
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3303#comment:2>
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

Reply via email to