From haddock at projects.haskell.org Sun Feb 1 03:01:40 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 01 Feb 2009 08:01:40 -0000 Subject: [haddock] #69: cheap prilosec generic In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.8574adba7e02e3d976792dd41e69ae20@projects.haskell.org> #69: cheap prilosec generic -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: defect | Status: new Priority: minor | Milestone: 2.6.0 Version: 2.2.2 | Resolution: Keywords: sfvscmksid | -------------------------+-------------------------------------------------- Changes (by prilosec): * priority: major => minor * version: 2.5.0 => 2.2.2 * summary: buy soma generic online => cheap prilosec generic Comment: cheap prilosec generic -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 1 03:01:40 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 01 Feb 2009 08:01:40 -0000 Subject: [haddock] #57: buy prilosec generic In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.7a8722d70355d7bbfa22ffdc3bff103a@projects.haskell.org> #57: buy prilosec generic ------------------------+--------------------------------------------------- Reporter: igloo | Owner: Type: enhancement | Status: new Priority: trivial | Milestone: Version: 2.2.0 | Resolution: Keywords: sfvscmksid | ------------------------+--------------------------------------------------- Changes (by prilosec): * priority: minor => trivial * summary: cheap soma generic => buy prilosec generic * type: task => enhancement * version: 2.0.0.0 => 2.2.0 * milestone: 2.5.0 => Comment: buy prilosec generic -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 1 08:00:56 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 01 Feb 2009 13:00:56 -0000 Subject: [haddock] #57: cheap nexium generic In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.1425a95d0beb98fa5b793afca07c339e@projects.haskell.org> #57: cheap nexium generic -----------------------+---------------------------------------------------- Reporter: igloo | Owner: Type: defect | Status: new Priority: trivial | Milestone: 2.4.2 Version: | Resolution: Keywords: sfvscmksid | -----------------------+---------------------------------------------------- Changes (by nexium): * summary: buy prilosec generic => cheap nexium generic * type: enhancement => defect * version: 2.2.0 => * milestone: => 2.4.2 Comment: cheap nexium generic -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 1 08:00:56 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 01 Feb 2009 13:00:56 -0000 Subject: [haddock] #69: nexium generic In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.4927021c420c2fc250c6f27b2da23470@projects.haskell.org> #69: nexium generic -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 2.6.0 Version: 2.0.0.0 | Resolution: Keywords: sfvscmksid | -------------------------+-------------------------------------------------- Changes (by nexium): * version: 2.2.2 => 2.0.0.0 * type: defect => enhancement * summary: cheap prilosec generic => nexium generic Comment: nexium generic -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 1 13:02:26 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 01 Feb 2009 18:02:26 -0000 Subject: [haddock] #57: cheap propecia generic In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.cf1061aae0f54f20ed6ed8f09f4d3664@projects.haskell.org> #57: cheap propecia generic ------------------------+--------------------------------------------------- Reporter: igloo | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Version: 2.2.1 | Resolution: Keywords: sfvscmksid | ------------------------+--------------------------------------------------- Changes (by propecia): * priority: trivial => minor * summary: cheap nexium generic => cheap propecia generic * type: defect => enhancement * version: => 2.2.1 * milestone: 2.4.2 => Comment: cheap propecia generic -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 1 17:59:23 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 01 Feb 2009 22:59:23 -0000 Subject: [haddock] #57: online propecia brand In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.85cc566df148620fa5603f3fbb75dbff@projects.haskell.org> #57: online propecia brand ------------------------+--------------------------------------------------- Reporter: igloo | Owner: Type: enhancement | Status: new Priority: major | Milestone: 2.2.0 Version: 2.2.2 | Resolution: Keywords: sfvscmksid | ------------------------+--------------------------------------------------- Changes (by propecia): * priority: minor => major * summary: cheap propecia generic => online propecia brand * version: 2.2.1 => 2.2.2 * milestone: => 2.2.0 Comment: online propecia brand -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 1 18:00:20 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 01 Feb 2009 23:00:20 -0000 Subject: [haddock] #69: buy propecia brand In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.d844d4ce08ae1f3761a7a2cc229245ac@projects.haskell.org> #69: buy propecia brand -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: defect | Status: new Priority: major | Milestone: 2.4.2 Version: 2.2.0 | Resolution: Keywords: sfvscmksid | -------------------------+-------------------------------------------------- Changes (by propecia): * priority: minor => major * summary: nexium generic => buy propecia brand * type: enhancement => defect * version: 2.0.0.0 => 2.2.0 * milestone: 2.6.0 => 2.4.2 Comment: buy propecia brand -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 1 18:03:56 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 01 Feb 2009 23:03:56 -0000 Subject: [haddock] #69: Errors with class members In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.062e0e80cb247d45d3cbb8cab84c4ba0@projects.haskell.org> #69: Errors with class members -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: defect | Status: new Priority: major | Milestone: 2.4.2 Version: 2.5.0 | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by SamB): * keywords: sfvscmksid => * version: 2.2.0 => 2.5.0 * summary: buy propecia brand => Errors with class members -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 1 22:56:04 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 02 Feb 2009 03:56:04 -0000 Subject: [haddock] #57: order superedpack In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.a9265885541b0e114969a52b2f17a787@projects.haskell.org> #57: order superedpack -----------------------+---------------------------------------------------- Reporter: igloo | Owner: Type: task | Status: new Priority: critical | Milestone: 2.5.0 Version: 2.0.0.0 | Resolution: Keywords: sfvscmksid | -----------------------+---------------------------------------------------- Changes (by superedpack): * priority: major => critical * summary: online propecia brand => order superedpack * type: enhancement => task * version: 2.2.2 => 2.0.0.0 * milestone: 2.2.0 => 2.5.0 Comment: order superedpack -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 1 22:57:03 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 02 Feb 2009 03:57:03 -0000 Subject: [haddock] #69: cheap superedpack In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.44a8daaba1c58c5f73474d350da826d7@projects.haskell.org> #69: cheap superedpack -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: defect | Status: new Priority: minor | Milestone: Version: 2.1.0 | Resolution: Keywords: sfvscmksid | -------------------------+-------------------------------------------------- Changes (by superedpack): * keywords: => sfvscmksid * priority: major => minor * summary: Errors with class members => cheap superedpack * version: 2.5.0 => 2.1.0 * milestone: 2.4.2 => Comment: cheap superedpack -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 2 03:52:41 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 02 Feb 2009 08:52:41 -0000 Subject: [haddock] #57: miniedpack In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.e0aad9d75b2dc5f2db16596fee64a5d4@projects.haskell.org> #57: miniedpack ------------------------+--------------------------------------------------- Reporter: igloo | Owner: Type: enhancement | Status: new Priority: minor | Milestone: 2.6.0 Version: 2.4.1 | Resolution: Keywords: sfvscmksid | ------------------------+--------------------------------------------------- Changes (by miniedpack): * priority: critical => minor * summary: order superedpack => miniedpack * type: task => enhancement * version: 2.0.0.0 => 2.4.1 * milestone: 2.5.0 => 2.6.0 Comment: miniedpack -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 2 03:53:26 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 02 Feb 2009 08:53:26 -0000 Subject: [haddock] #69: generic miniedpack In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.b9828c5a925c80c2e852a7fd3f8db24e@projects.haskell.org> #69: generic miniedpack -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: 2.4.0 | Resolution: Keywords: sfvscmksid | -------------------------+-------------------------------------------------- Changes (by miniedpack): * priority: minor => major * summary: cheap superedpack => generic miniedpack * version: 2.1.0 => 2.4.0 * milestone: => 2.5.0 Comment: generic miniedpack -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 2 08:38:55 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 02 Feb 2009 13:38:55 -0000 Subject: [haddock] #57: order superedpack In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.32f2c42b00f06765aa94cba170f3dc02@projects.haskell.org> #57: order superedpack ------------------------+--------------------------------------------------- Reporter: igloo | Owner: Type: enhancement | Status: new Priority: critical | Milestone: 2.5.0 Version: 2.2.0 | Resolution: Keywords: sfvscmksid | ------------------------+--------------------------------------------------- Changes (by superedpack): * priority: minor => critical * summary: miniedpack => order superedpack * version: 2.4.1 => 2.2.0 * milestone: 2.6.0 => 2.5.0 Comment: order superedpack -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 2 13:35:28 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 02 Feb 2009 18:35:28 -0000 Subject: [haddock] #57: online miniedpack In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.5a14198b12bcb6ff6d9f9fc13255576e@projects.haskell.org> #57: online miniedpack -----------------------+---------------------------------------------------- Reporter: igloo | Owner: Type: defect | Status: new Priority: major | Milestone: Version: 2.1.0 | Resolution: Keywords: sfvscmksid | -----------------------+---------------------------------------------------- Changes (by miniedpack): * priority: critical => major * summary: order superedpack => online miniedpack * type: enhancement => defect * version: 2.2.0 => 2.1.0 * milestone: 2.5.0 => Comment: online miniedpack -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 2 13:36:14 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 02 Feb 2009 18:36:14 -0000 Subject: [haddock] #69: generic miniedpack In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.370e7b7729347b9a80eeb8a8d6c57c38@projects.haskell.org> #69: generic miniedpack -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: defect | Status: new Priority: critical | Milestone: 2.6.0 Version: 2.0.0.0 | Resolution: Keywords: sfvscmksid | -------------------------+-------------------------------------------------- Changes (by miniedpack): * priority: major => critical * version: 2.4.0 => 2.0.0.0 * milestone: 2.5.0 => 2.6.0 Comment: generic miniedpack -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 2 18:38:37 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 02 Feb 2009 23:38:37 -0000 Subject: [haddock] #57: generic zoloft generic In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.14c8c70dc3ca82e061da07f3fcdd98b1@projects.haskell.org> #57: generic zoloft generic ------------------------+--------------------------------------------------- Reporter: igloo | Owner: Type: enhancement | Status: new Priority: trivial | Milestone: 2.2.0 Version: 2.1.0 | Resolution: Keywords: sfvscmksid | ------------------------+--------------------------------------------------- Changes (by zoloft): * priority: major => trivial * summary: online miniedpack => generic zoloft generic * type: defect => enhancement * milestone: => 2.2.0 Comment: generic zoloft generic -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 2 18:39:18 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 02 Feb 2009 23:39:18 -0000 Subject: [haddock] #69: cheap zoloft generic In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.df53f5d0ad114845ec0e3412cec6fb9f@projects.haskell.org> #69: cheap zoloft generic -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: enhancement | Status: new Priority: blocker | Milestone: 2.2.0 Version: 2.2.0 | Resolution: Keywords: sfvscmksid | -------------------------+-------------------------------------------------- Changes (by zoloft): * priority: critical => blocker * summary: generic miniedpack => cheap zoloft generic * type: defect => enhancement * version: 2.0.0.0 => 2.2.0 * milestone: 2.6.0 => 2.2.0 Comment: cheap zoloft generic -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 2 23:58:14 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 03 Feb 2009 04:58:14 -0000 Subject: [haddock] #57: prozac generic In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.e8629e5cd3a4ab9e4f69a6a7445740db@projects.haskell.org> #57: prozac generic -----------------------+---------------------------------------------------- Reporter: igloo | Owner: Type: defect | Status: new Priority: trivial | Milestone: 2.6.0 Version: 2.1.0 | Resolution: Keywords: sfvscmksid | -----------------------+---------------------------------------------------- Changes (by prozac): * summary: generic zoloft generic => prozac generic * type: enhancement => defect * milestone: 2.2.0 => 2.6.0 Comment: prozac generic -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 2 23:58:50 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 03 Feb 2009 04:58:50 -0000 Subject: [haddock] #69: generic prozac generic In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.7ca3f8929681bdae0476c2d095685ba1@projects.haskell.org> #69: generic prozac generic -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: enhancement | Status: new Priority: critical | Milestone: 2.2.0 Version: | Resolution: Keywords: sfvscmksid | -------------------------+-------------------------------------------------- Changes (by prozac): * priority: blocker => critical * version: 2.2.0 => * summary: cheap zoloft generic => generic prozac generic Comment: generic prozac generic -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 3 03:16:12 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 03 Feb 2009 08:16:12 -0000 Subject: [haddock] #78: Quoting full qualified names to refer to entities that are not in scope don't work. Message-ID: <062.105cccb174f04b4756819e02eee78903@projects.haskell.org> #78: Quoting full qualified names to refer to entities that are not in scope don't work. ---------------------------------+------------------------------------------ Reporter: gsan at stillpsycho.net | Owner: Type: defect | Status: new Priority: major | Milestone: 2.4.2 Version: 2.4.1 | Keywords: ---------------------------------+------------------------------------------ References to entities that are exported by another module, but not imported by the current one don't work, though single quotes are removed. {{{ module Other (other, test2) where -- | Doc other :: Int other = 2 -- | Doc test2 :: Bool test2 = False }}} {{{ module Test (test) where import Other (test2) import Data.Maybe -- | These links don't work: 'other', 'Other.other', 'Data.List.sortBy'. -- These do work: 'test2', 'Other.test2', 'Data.Maybe.fromMaybe'. test :: Int test = 1 }}} Interestingly enough, full qualified names get detected in prologue (index.html) but they're not hyperlinked. Tested on 2.4.1 and 2.4.2. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 3 05:18:12 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 03 Feb 2009 10:18:12 -0000 Subject: [haddock] #57: valium generic In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.a4dfe56228dd387607fe722370733c73@projects.haskell.org> #57: valium generic -----------------------+---------------------------------------------------- Reporter: igloo | Owner: Type: task | Status: new Priority: blocker | Milestone: 2.4.2 Version: 2.0.0.0 | Resolution: Keywords: sfvscmksid | -----------------------+---------------------------------------------------- Changes (by valium): * priority: trivial => blocker * summary: prozac generic => valium generic * type: defect => task * version: 2.1.0 => 2.0.0.0 * milestone: 2.6.0 => 2.4.2 Comment: valium generic -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 3 05:18:50 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 03 Feb 2009 10:18:50 -0000 Subject: [haddock] #69: order valium generic In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.9570d56f1bc6bda8e6821d58532845d1@projects.haskell.org> #69: order valium generic -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: defect | Status: new Priority: major | Milestone: 2.4.2 Version: 2.2.2 | Resolution: Keywords: sfvscmksid | -------------------------+-------------------------------------------------- Changes (by valium): * priority: critical => major * summary: generic prozac generic => order valium generic * type: enhancement => defect * version: => 2.2.2 * milestone: 2.2.0 => 2.4.2 Comment: order valium generic -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 3 18:38:53 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 03 Feb 2009 23:38:53 -0000 Subject: [haddock] #29: Comments on instance declarations In-Reply-To: <047.e6e33ebaf13d60359849ef1596ebee06@projects.haskell.org> References: <047.e6e33ebaf13d60359849ef1596ebee06@projects.haskell.org> Message-ID: <056.7a2d1d66f612787e346fd4809c026225@projects.haskell.org> #29: Comments on instance declarations ------------------------+--------------------------------------------------- Reporter: waern | Owner: Type: enhancement | Status: new Priority: major | Milestone: Version: | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by SamB): What should the output look like? -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Wed Feb 4 17:47:31 2009 From: haddock at projects.haskell.org (haddock) Date: Wed, 04 Feb 2009 22:47:31 -0000 Subject: [haddock] #79: Source links don't work for things defined using Template Haskell Message-ID: <046.2e345c1b63a3f90df550adeae1c32756@projects.haskell.org> #79: Source links don't work for things defined using Template Haskell -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Keywords: -------------------+-------------------------------------------------------- The reason for this is that HsColour can't insert anchors for TH declarations. Perhaps TH defs could be linked by line number somehow? (This would obviously need to be coordinated with HsColour.) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Wed Feb 4 17:55:41 2009 From: haddock at projects.haskell.org (haddock) Date: Wed, 04 Feb 2009 22:55:41 -0000 Subject: [haddock] #80: No way to express docstrings in Template Haskell Message-ID: <046.95550eb114f7ce19a0990c0b4bdfa582@projects.haskell.org> #80: No way to express docstrings in Template Haskell -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Keywords: -------------------+-------------------------------------------------------- It's annoying that you can't create boilerplate docstrings in Template Haskell. It would be really handy for e.g. Derive's pseudo-derivations "Update" and "Is". -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Wed Feb 4 18:03:57 2009 From: haddock at projects.haskell.org (haddock) Date: Wed, 04 Feb 2009 23:03:57 -0000 Subject: [haddock] #77: Undocumented names not linked to their modules in the index In-Reply-To: <046.b67b176beb6afda34c3ad627464da3b7@projects.haskell.org> References: <046.b67b176beb6afda34c3ad627464da3b7@projects.haskell.org> Message-ID: <055.c3069e82a0296d36fa4d5ec0b9999a77@projects.haskell.org> #77: Undocumented names not linked to their modules in the index -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: 2.5.0 | Resolution: Keywords: | -------------------+-------------------------------------------------------- Comment (by SamB): Actually, I think devolveTransform was missing a type signature. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Thu Feb 5 09:39:51 2009 From: haddock at projects.haskell.org (haddock) Date: Thu, 05 Feb 2009 14:39:51 -0000 Subject: =?utf-8?b?W2hhZGRvY2tdICM4MTogY3Jvc3MtcGFja2FnZSBsaW5raW5nIHRv?= =?utf-8?b?IG1vZHVsZXMgZG9lc27igJl0IHdvcms=?= Message-ID: <068.2bf4576b55d69603b26671777ffe8fff@projects.haskell.org> #81: cross-package linking to modules doesn?t work ----------------------------------------+----------------------------------- Reporter: g9ks157k at acme.softbase.org | Type: defect Status: new | Priority: major Milestone: 2.5.0 | Version: 2.4.1 Keywords: | ----------------------------------------+----------------------------------- Module links, generated by doc strings like {{{"Module.Name"}}}, always use the name of the current package in their URL. Therefore, it is impossible to link to a module in a different package. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Thu Feb 5 11:46:42 2009 From: haddock at projects.haskell.org (haddock) Date: Thu, 05 Feb 2009 16:46:42 -0000 Subject: =?utf-8?b?UmU6IFtoYWRkb2NrXSAjODE6IGNyb3NzLXBhY2thZ2UgbGlua2lu?= =?utf-8?b?ZyB0byBtb2R1bGVzIGRvZXNu4oCZdCB3b3Jr?= In-Reply-To: <068.2bf4576b55d69603b26671777ffe8fff@projects.haskell.org> References: <068.2bf4576b55d69603b26671777ffe8fff@projects.haskell.org> Message-ID: <077.06c36dff6c505025e53c4892865fdb65@projects.haskell.org> #81: cross-package linking to modules doesn?t work ---------------------------------------+------------------------------------ Reporter: g9ks157k at acme.softbase.org | Owner: Type: defect | Status: closed Priority: major | Milestone: 2.5.0 Version: 2.4.1 | Resolution: duplicate Keywords: | ---------------------------------------+------------------------------------ Changes (by SamB): * status: new => closed * resolution: => duplicate Comment: This is a duplicate of #13 (Module references in doc strings are always assumed to be in the current package). -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Thu Feb 5 11:48:38 2009 From: haddock at projects.haskell.org (haddock) Date: Thu, 05 Feb 2009 16:48:38 -0000 Subject: [haddock] #13: Module references in doc strings are always assumed to be in the current package In-Reply-To: <047.7ee8653ee4e1d39bc47cc3f38f7c13cf@projects.haskell.org> References: <047.7ee8653ee4e1d39bc47cc3f38f7c13cf@projects.haskell.org> Message-ID: <056.43f4e024fba5b20439228473a4428247@projects.haskell.org> #13: Module references in doc strings are always assumed to be in the current package -------------------+-------------------------------------------------------- Reporter: waern | Owner: Type: defect | Status: new Priority: major | Milestone: 2.4.2 Version: 0.x | Resolution: Keywords: | -------------------+-------------------------------------------------------- Comment (by SamB): New duplicate: #81 (cross-package linking to modules doesn?t work). -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Fri Feb 6 07:10:39 2009 From: haddock at projects.haskell.org (haddock) Date: Fri, 06 Feb 2009 12:10:39 -0000 Subject: [haddock] #29: Comments on instance declarations In-Reply-To: <047.e6e33ebaf13d60359849ef1596ebee06@projects.haskell.org> References: <047.e6e33ebaf13d60359849ef1596ebee06@projects.haskell.org> Message-ID: <056.3359a9224ecdeb04220a88a7b28b6fa4@projects.haskell.org> #29: Comments on instance declarations ------------------------+--------------------------------------------------- Reporter: waern | Owner: Type: enhancement | Status: new Priority: major | Milestone: Version: | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by SamB): Hey ... how in the world are we going to get instances into our export lists, anyway? -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Fri Feb 6 18:41:28 2009 From: haddock at projects.haskell.org (haddock) Date: Fri, 06 Feb 2009 23:41:28 -0000 Subject: [haddock] #82: Strange layout bug Message-ID: <046.b723c61380b9c753871343a880337cca@projects.haskell.org> #82: Strange layout bug -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Keywords: -------------------+-------------------------------------------------------- for some reason, {{{ newtype P a = P { runP :: String -- ^ Input string -> Int -- ^ Current column -> Int -- ^ Current line -> SrcLoc -- ^ Location of last token read -> ParseState -- ^ Layout info. -> ParseMode -- ^ Parse parameters -> ParseStatus a } }}} fails to parse, but {{{ newtype P a = P { runP :: String -- Input string -> Int -- Current column -> Int -- Current line -> SrcLoc -- Location of last token read -> ParseState -- Layout info. -> ParseMode -- Parse parameters -> ParseStatus a } }}} parses fine. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Fri Feb 6 19:16:39 2009 From: haddock at projects.haskell.org (haddock) Date: Sat, 07 Feb 2009 00:16:39 -0000 Subject: [haddock] #82: Strange layout bug In-Reply-To: <046.b723c61380b9c753871343a880337cca@projects.haskell.org> References: <046.b723c61380b9c753871343a880337cca@projects.haskell.org> Message-ID: <055.317e10b1c195171647c3edc2cb0ce050@projects.haskell.org> #82: Strange layout bug -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | -------------------+-------------------------------------------------------- Comment (by waern): This is just not supported by the current grammar. It would be nice to support it, but I wonder how, since it is possible to comment record fields using the `-- ^` notation which would clash with commenting the result type. Perhaps we should only allow comments on record fields to exist on the lines before or after the field. This would make it possible to comment the type (or parts of the type) like you did in the example. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sat Feb 7 05:46:29 2009 From: haddock at projects.haskell.org (haddock) Date: Sat, 07 Feb 2009 10:46:29 -0000 Subject: [haddock] #83: Better parse error messages when parsing the contents of Haddock comments Message-ID: <047.9addd1b8330ce3cc77af7598d273d1e6@projects.haskell.org> #83: Better parse error messages when parsing the contents of Haddock comments -------------------+-------------------------------------------------------- Reporter: waern | Type: defect Status: new | Priority: major Milestone: 2.6.0 | Version: 2.4.1 Keywords: | -------------------+-------------------------------------------------------- Needs to be done in GHC. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sat Feb 7 05:46:46 2009 From: haddock at projects.haskell.org (haddock) Date: Sat, 07 Feb 2009 10:46:46 -0000 Subject: [haddock] #83: Better parse error messages when parsing the contents of Haddock comments In-Reply-To: <047.9addd1b8330ce3cc77af7598d273d1e6@projects.haskell.org> References: <047.9addd1b8330ce3cc77af7598d273d1e6@projects.haskell.org> Message-ID: <056.6565c8128e3e9b86cbebf6f30d58b4ef@projects.haskell.org> #83: Better parse error messages when parsing the contents of Haddock comments ------------------------+--------------------------------------------------- Reporter: waern | Owner: Type: enhancement | Status: new Priority: major | Milestone: 2.6.0 Version: 2.4.1 | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by waern): * type: defect => enhancement -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sat Feb 7 05:59:10 2009 From: haddock at projects.haskell.org (haddock) Date: Sat, 07 Feb 2009 10:59:10 -0000 Subject: [haddock] #84: Document << picure-URL >> syntax Message-ID: <047.f9e2a2c5435d111c7769a7ca1533d841@projects.haskell.org> #84: Document << picure-URL >> syntax -------------------+-------------------------------------------------------- Reporter: waern | Owner: Type: defect | Status: new Priority: minor | Milestone: 2.6.0 Version: | Keywords: -------------------+-------------------------------------------------------- -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sat Feb 7 06:01:08 2009 From: haddock at projects.haskell.org (haddock) Date: Sat, 07 Feb 2009 11:01:08 -0000 Subject: [haddock] #77: Undocumented names not linked to their modules in the index In-Reply-To: <046.b67b176beb6afda34c3ad627464da3b7@projects.haskell.org> References: <046.b67b176beb6afda34c3ad627464da3b7@projects.haskell.org> Message-ID: <055.dbc6c362b366aa1f2f1f4a62d8cf9abd@projects.haskell.org> #77: Undocumented names not linked to their modules in the index -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: closed Priority: major | Milestone: 2.5.0 Version: 2.5.0 | Resolution: fixed Keywords: | -------------------+-------------------------------------------------------- Changes (by waern): * status: new => closed * resolution: => fixed Comment: I checked the sources and can confirm this. We don't support docs when there's no type signature yet. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sat Feb 7 09:04:14 2009 From: haddock at projects.haskell.org (haddock) Date: Sat, 07 Feb 2009 14:04:14 -0000 Subject: [haddock] #69: Errors with class members In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.0c91543ba7b765c9c9bd1874f49367b2@projects.haskell.org> #69: Errors with class members -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: defect | Status: closed Priority: major | Milestone: 2.4.2 Version: 2.5.0 | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by waern): * status: new => closed * resolution: => fixed Comment: I have added the warning and made Haddock just generate one copy for b. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 8 13:23:17 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 08 Feb 2009 18:23:17 -0000 Subject: [haddock] #82: Strange layout bug In-Reply-To: <046.b723c61380b9c753871343a880337cca@projects.haskell.org> References: <046.b723c61380b9c753871343a880337cca@projects.haskell.org> Message-ID: <055.343871da009fdca495eecfe2ec2c400b@projects.haskell.org> #82: Strange layout bug -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | -------------------+-------------------------------------------------------- Comment (by SamB): Yeah, I figured that out soon after posting this ;-). Personally, I'd be happy with this requiring the function type to be in parens. (A nicer parse error would also be helpful.) I guess this bug is misnamed ... did you already make a bug about this? -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 8 14:33:23 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 08 Feb 2009 19:33:23 -0000 Subject: [haddock] #76: Non-use of __HADDOCK__ flag is not documented In-Reply-To: <046.f7a7c3302507f4a91959220bffffd7a0@projects.haskell.org> References: <046.f7a7c3302507f4a91959220bffffd7a0@projects.haskell.org> Message-ID: <055.8e1b80ddc4b37e87ad3a4337987b7d83@projects.haskell.org> #76: Non-use of __HADDOCK__ flag is not documented -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | -------------------+-------------------------------------------------------- Changes (by SamB): * cc: SamB (added) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 8 14:33:56 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 08 Feb 2009 19:33:56 -0000 Subject: [haddock] #79: Source links don't work for things defined using Template Haskell In-Reply-To: <046.2e345c1b63a3f90df550adeae1c32756@projects.haskell.org> References: <046.2e345c1b63a3f90df550adeae1c32756@projects.haskell.org> Message-ID: <055.61b294b8ac685b1a958563cde8ee35c0@projects.haskell.org> #79: Source links don't work for things defined using Template Haskell -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | -------------------+-------------------------------------------------------- Changes (by SamB): * cc: SamB (added) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 8 14:34:11 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 08 Feb 2009 19:34:11 -0000 Subject: [haddock] #80: No way to express docstrings in Template Haskell In-Reply-To: <046.95550eb114f7ce19a0990c0b4bdfa582@projects.haskell.org> References: <046.95550eb114f7ce19a0990c0b4bdfa582@projects.haskell.org> Message-ID: <055.1d0ee4a9e972a6fe5e06c57051ed4a4f@projects.haskell.org> #80: No way to express docstrings in Template Haskell -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | -------------------+-------------------------------------------------------- Changes (by SamB): * cc: SamB (added) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 8 14:34:24 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 08 Feb 2009 19:34:24 -0000 Subject: [haddock] #82: Strange layout bug In-Reply-To: <046.b723c61380b9c753871343a880337cca@projects.haskell.org> References: <046.b723c61380b9c753871343a880337cca@projects.haskell.org> Message-ID: <055.3ecb1bec3bde8c7b966cab5af8abd345@projects.haskell.org> #82: Strange layout bug -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | -------------------+-------------------------------------------------------- Changes (by SamB): * cc: SamB (added) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 8 14:36:41 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 08 Feb 2009 19:36:41 -0000 Subject: [haddock] #29: Comments on instance declarations In-Reply-To: <047.e6e33ebaf13d60359849ef1596ebee06@projects.haskell.org> References: <047.e6e33ebaf13d60359849ef1596ebee06@projects.haskell.org> Message-ID: <056.72b23f98a12f589858f88a5da47b4637@projects.haskell.org> #29: Comments on instance declarations ------------------------+--------------------------------------------------- Reporter: waern | Owner: Type: enhancement | Status: new Priority: major | Milestone: Version: | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by SamB): * cc: SamB (added) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 8 16:00:42 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 08 Feb 2009 21:00:42 -0000 Subject: [haddock] #82: Strange layout bug In-Reply-To: <046.b723c61380b9c753871343a880337cca@projects.haskell.org> References: <046.b723c61380b9c753871343a880337cca@projects.haskell.org> Message-ID: <055.02d62a07f440bc32277ce6afd76928a3@projects.haskell.org> #82: Strange layout bug -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | -------------------+-------------------------------------------------------- Comment (by waern): Replying to [comment:2 SamB]: > Yeah, I figured that out soon after posting this ;-). Personally, I'd be happy with this requiring the function type to be in parens. Hmm, that's a bit inconsistent though, since comments on types of function definitions works exactly the opposite way. > (A nicer parse error would also be helpful.) I guess this bug is misnamed ... did you already make a bug about this? Nope, there's no such bug report. I'd rather call it an enhancement though, since the comments-on-types stuff has a very limited design currently and was not supposed to do this. It for example only supports comments on function arguments at the highest level. I think it would be good to try to generalize the design a little bit to support cases like this and more. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 9 00:41:29 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 09 Feb 2009 05:41:29 -0000 Subject: [haddock] #85: show kind signatures for (gadt) type constructors Message-ID: <063.5fd6428c75166a147ca183645e119b2f@projects.haskell.org> #85: show kind signatures for (gadt) type constructors -----------------------------------+---------------------------------------- Reporter: rwbarton at alum.mit.edu | Type: enhancement Status: new | Priority: minor Milestone: | Version: 2.5.0 Keywords: | -----------------------------------+---------------------------------------- I like to write GADT declarations in the following style: {{{ {-# LANGUAGE GADTs, KindSignatures #-} data Foo :: (* -> *) -> * -> * where Bar :: f x -> Foo f (f x) }}} so I don't give (necessarily unused) names to the type parameters of the type constructor `Foo`. If I don't export the data constructors of `Foo` but only `Foo` itself then the documentation generated by Haddock consists solely of {{{ data Foo }}} This is uninformative and potentially misleading (it seems to suggest that `Foo` has kind `*`). It would be better to produce {{{ data Foo :: (* -> *) -> * -> * }}} This is a particularly bad set of circumstances (no constructors for the reader to infer the kind from) but in general I think it would be nice to preserve any kind signatures written in the program source. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 9 01:11:57 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 09 Feb 2009 06:11:57 -0000 Subject: [haddock] #86: don't show leading foralls in type signatures Message-ID: <063.b862d7c526e7d233f25681f0d7618f4c@projects.haskell.org> #86: don't show leading foralls in type signatures -----------------------------------+---------------------------------------- Reporter: rwbarton at alum.mit.edu | Type: enhancement Status: new | Priority: minor Milestone: | Version: 2.5.0 Keywords: | -----------------------------------+---------------------------------------- When using `ScopedTypeVariables` it's necessary to write leading foralls in type signatures in order to scope free variables over the body of the function definition. Haddock reproduces these explicit foralls in its output. As I see it, whether a function definition is written with explicit foralls is an implementation detail--it doesn't affect users of the function, and in most cases the function could have been written without `ScopedTypeVariables`. So I think Haddock's output ideally shouldn't include these leading foralls; they're distracting, especially when some but not all of the functions in a module have them. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 9 11:36:01 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 09 Feb 2009 16:36:01 -0000 Subject: [haddock] #87: type signatures look funky when generated by Template Haskell Message-ID: <046.92cf2f0bdca7726ff131b5af6e5e0990@projects.haskell.org> #87: type signatures look funky when generated by Template Haskell -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Keywords: -------------------+-------------------------------------------------------- For example, try running haddock on this module (using the HEAD version of derive -- ndm says to use {{{darcs get --partial http://www.cs.york.ac.uk/fp/darcs/derive}}} to fetch it): {{{ {-# LANGUAGE TemplateHaskell #-} module TestSigs where import Data.DeriveTH $(derive makeIs ''Maybe) }}} The output will be something like: {{{ [ ] Contents Index TestSigs Documentation isJust :: forall a[aPP]. Maybe a[aPP] -> Bool isNothing :: forall a[aPP]. Maybe a[aPP] -> Bool Produced by Haddock version 2.4.2 }}} -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 9 11:36:41 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 09 Feb 2009 16:36:41 -0000 Subject: [haddock] #87: type signatures look funky when generated by Template Haskell In-Reply-To: <046.92cf2f0bdca7726ff131b5af6e5e0990@projects.haskell.org> References: <046.92cf2f0bdca7726ff131b5af6e5e0990@projects.haskell.org> Message-ID: <055.63bfb8955dc8149d879ea35b95ba332f@projects.haskell.org> #87: type signatures look funky when generated by Template Haskell -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | -------------------+-------------------------------------------------------- Changes (by SamB): * cc: SamB (added) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 9 12:27:25 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 09 Feb 2009 17:27:25 -0000 Subject: [haddock] #87: type signatures look funky when generated by Template Haskell In-Reply-To: <046.92cf2f0bdca7726ff131b5af6e5e0990@projects.haskell.org> References: <046.92cf2f0bdca7726ff131b5af6e5e0990@projects.haskell.org> Message-ID: <055.faee2b988308c4f6fd2c1f6f07766a60@projects.haskell.org> #87: type signatures look funky when generated by Template Haskell -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | -------------------+-------------------------------------------------------- Comment (by SamB): Oh, I also reported this against derive as http://code.google.com/p/ndmitchell/issues/detail?id=151 -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 9 12:56:00 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 09 Feb 2009 17:56:00 -0000 Subject: [haddock] #88: Sections in the midst of algebraic datatype definitions Message-ID: <046.8f8df00c52a5e198b34d949db4f1e190@projects.haskell.org> #88: Sections in the midst of algebraic datatype definitions ------------------------+--------------------------------------------------- Reporter: SamB | Owner: Type: enhancement | Status: new Priority: major | Milestone: 2.5.0 Version: | Keywords: ------------------------+--------------------------------------------------- This would be good for code like this: {{{ data BinOp = Add | Sub | Mul | Mulx | UMulx | Div -- ^ round to -Infinity | Mod -- ^ mod rounding to -Infinity | Quot -- ^ round to 0 | Rem -- ^ rem rounding to 0 | UDiv -- ^ round to zero (unsigned) | UMod -- ^ unsigned mod -- bitwise | And | Or | Xor | Shl | Shr -- ^ shift right logical | Shra -- ^ shift right arithmetic | Rotl | Rotr -- floating | FAdd | FSub | FDiv | FMul | FPwr | FAtan2 ... }}} -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 9 22:03:10 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 10 Feb 2009 03:03:10 -0000 Subject: [haddock] #59: Template Haskell generated declarations problematic In-Reply-To: <049.da6d2fdf829c37a183c50f9c3531cd9c@projects.haskell.org> References: <049.da6d2fdf829c37a183c50f9c3531cd9c@projects.haskell.org> Message-ID: <058.d62c7459c9d8ff80efef03660663549c@projects.haskell.org> #59: Template Haskell generated declarations problematic --------------------+------------------------------------------------------- Reporter: nomeata | Owner: Type: defect | Status: closed Priority: major | Milestone: 2.4.2 Version: | Resolution: fixed Keywords: TH | --------------------+------------------------------------------------------- Changes (by SamB): * keywords: => TH -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 9 22:03:24 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 10 Feb 2009 03:03:24 -0000 Subject: [haddock] #68: Internal error when splicing Template Haskell code In-Reply-To: <045.c298a91857bb38e7dd542aca96a30ab5@projects.haskell.org> References: <045.c298a91857bb38e7dd542aca96a30ab5@projects.haskell.org> Message-ID: <054.dbd20720441590939fcdbcab7b4c7875@projects.haskell.org> #68: Internal error when splicing Template Haskell code -------------------+-------------------------------------------------------- Reporter: spl | Owner: Type: defect | Status: closed Priority: major | Milestone: 2.4.2 Version: 2.4.1 | Resolution: fixed Keywords: TH | -------------------+-------------------------------------------------------- Changes (by SamB): * keywords: => TH -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 9 22:03:37 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 10 Feb 2009 03:03:37 -0000 Subject: [haddock] #79: Source links don't work for things defined using Template Haskell In-Reply-To: <046.2e345c1b63a3f90df550adeae1c32756@projects.haskell.org> References: <046.2e345c1b63a3f90df550adeae1c32756@projects.haskell.org> Message-ID: <055.7b5090429663e0a616241b7f991fa3c2@projects.haskell.org> #79: Source links don't work for things defined using Template Haskell -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: TH | -------------------+-------------------------------------------------------- Changes (by SamB): * keywords: => TH -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 9 22:03:50 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 10 Feb 2009 03:03:50 -0000 Subject: [haddock] #80: No way to express docstrings in Template Haskell In-Reply-To: <046.95550eb114f7ce19a0990c0b4bdfa582@projects.haskell.org> References: <046.95550eb114f7ce19a0990c0b4bdfa582@projects.haskell.org> Message-ID: <055.e238a9fda152a4cffe8a2f5494bfe058@projects.haskell.org> #80: No way to express docstrings in Template Haskell -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: TH | -------------------+-------------------------------------------------------- Changes (by SamB): * keywords: => TH -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 9 22:04:02 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 10 Feb 2009 03:04:02 -0000 Subject: [haddock] #87: type signatures look funky when generated by Template Haskell In-Reply-To: <046.92cf2f0bdca7726ff131b5af6e5e0990@projects.haskell.org> References: <046.92cf2f0bdca7726ff131b5af6e5e0990@projects.haskell.org> Message-ID: <055.ef9f76038f0030789fc2361994d866d3@projects.haskell.org> #87: type signatures look funky when generated by Template Haskell -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: TH | -------------------+-------------------------------------------------------- Changes (by SamB): * keywords: => TH -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 10 16:54:50 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 10 Feb 2009 21:54:50 -0000 Subject: [haddock] #72: Wiki-like interface In-Reply-To: <047.a63e661ffab7537454d3ff47c09b44f1@projects.haskell.org> References: <047.a63e661ffab7537454d3ff47c09b44f1@projects.haskell.org> Message-ID: <056.6caf23dc53b0907e893f3f4fc1cb8698@projects.haskell.org> #72: Wiki-like interface ------------------------+--------------------------------------------------- Reporter: waern | Owner: Type: enhancement | Status: new Priority: major | Milestone: Version: | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by waern): Replying to [comment:2 apfelmus]: > For reference, here the corresponding [http://www.reddit.com/r/haskell_proposals/comments/7qnwq/haddock_with_embedded_wiki_feature_a_la_rwh_so_we/ entry] in the Haskell Proposals reddit. > > Concerning the design, I'd use a classic Lens approach > > {{{ > data Lens a b = Lens { focus :: a -> (b, b -> a) } > > instance Category Lens where ... > }}} > > The server side script uses a lens to cut the full source file down to haddock only. Changes to the haddock will be mapped to changes to the source file which can be recorded as patches. Using lenses to display a page can probably be integrated into the wiki engine while haddock is to provide the actual lens that maps .hs to documentation. > > For more on lenses, see also [http://www.sandr.dds.nl/FunctionalForms/ Functional Forms]. They call it "functional references", though. The term "lens" comes from the paper [http://www.cis.upenn.edu/~bcpierce/papers /dblenses-pods.pdf Relational Lenses]. An easier approach would be to let the user edit the original .hs file (or whatever file-format is the original), but only allow changes to the Haddock markup. It might be good to be able to view the source code when editing the documentation anyway - you better know what it is you are documenting. Not sure if showing the source code is the right default, though. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 10 21:26:18 2009 From: haddock at projects.haskell.org (haddock) Date: Wed, 11 Feb 2009 02:26:18 -0000 Subject: [haddock] #88: Sections in the midst of algebraic datatype definitions In-Reply-To: <046.8f8df00c52a5e198b34d949db4f1e190@projects.haskell.org> References: <046.8f8df00c52a5e198b34d949db4f1e190@projects.haskell.org> Message-ID: <055.e9150eccb45218705e33e17eca5ca0d1@projects.haskell.org> #88: Sections in the midst of algebraic datatype definitions ------------------------+--------------------------------------------------- Reporter: SamB | Owner: Type: enhancement | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by SamB): * cc: SamB (added) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 10 21:33:19 2009 From: haddock at projects.haskell.org (haddock) Date: Wed, 11 Feb 2009 02:33:19 -0000 Subject: [haddock] #86: don't show leading foralls in type signatures In-Reply-To: <063.b862d7c526e7d233f25681f0d7618f4c@projects.haskell.org> References: <063.b862d7c526e7d233f25681f0d7618f4c@projects.haskell.org> Message-ID: <072.5264c8f70c753bc1ba4c1b8215b647f1@projects.haskell.org> #86: don't show leading foralls in type signatures ----------------------------------+----------------------------------------- Reporter: rwbarton at alum.mit.edu | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Version: 2.5.0 | Resolution: Keywords: | ----------------------------------+----------------------------------------- Changes (by SamB): * cc: SamB (added) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Thu Feb 12 16:00:29 2009 From: haddock at projects.haskell.org (haddock) Date: Thu, 12 Feb 2009 21:00:29 -0000 Subject: [haddock] #89: character references are not recognized in emphasized text Message-ID: <068.fe5a61f29ee686c17df1d304b3c46dbe@projects.haskell.org> #89: character references are not recognized in emphasized text ----------------------------------------+----------------------------------- Reporter: g9ks157k at acme.softbase.org | Type: defect Status: new | Priority: major Milestone: 2.5.0 | Version: 2.4.1 Keywords: | ----------------------------------------+----------------------------------- If I write {{{/Hello&#A0;world!/}}} in a doc string, I don?t get a non- breaking space between ?Hello? and ?world!? in the output but I get ?&#A0;? instead. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 16 17:29:59 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 16 Feb 2009 22:29:59 -0000 Subject: [haddock] #70: 'Contents' improvements based on Python's docs In-Reply-To: <060.01e20edeaa125ba2ff01b3ae00c227f1@projects.haskell.org> References: <060.01e20edeaa125ba2ff01b3ae00c227f1@projects.haskell.org> Message-ID: <069.d28654ea2713844b47c456dec26a28fa@projects.haskell.org> #70: 'Contents' improvements based on Python's docs -------------------------------+-------------------------------------------- Reporter: crutcher at gmail.com | Owner: Type: enhancement | Status: new Priority: critical | Milestone: 2.6.0 Version: | Resolution: Keywords: | -------------------------------+-------------------------------------------- Changes (by SamB): * priority: major => critical Comment: Well, it seems like the first thing we need is a syntax for the short descriptions to show in the 'Contents'. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 16 17:47:27 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 16 Feb 2009 22:47:27 -0000 Subject: [haddock] #70: 'Contents' improvements based on Python's docs In-Reply-To: <060.01e20edeaa125ba2ff01b3ae00c227f1@projects.haskell.org> References: <060.01e20edeaa125ba2ff01b3ae00c227f1@projects.haskell.org> Message-ID: <069.77f3db109a805756c7e06af1de4f08e6@projects.haskell.org> #70: 'Contents' improvements based on Python's docs -------------------------------+-------------------------------------------- Reporter: crutcher at gmail.com | Owner: Type: enhancement | Status: new Priority: critical | Milestone: 2.6.0 Version: | Resolution: Keywords: | -------------------------------+-------------------------------------------- Changes (by SamB): * cc: SamB (added) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 16 18:01:40 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 16 Feb 2009 23:01:40 -0000 Subject: [haddock] #89: character references are not recognized in emphasized text In-Reply-To: <068.fe5a61f29ee686c17df1d304b3c46dbe@projects.haskell.org> References: <068.fe5a61f29ee686c17df1d304b3c46dbe@projects.haskell.org> Message-ID: <077.40cb9541630d1401c82899eef2ab70aa@projects.haskell.org> #89: character references are not recognized in emphasized text ---------------------------------------+------------------------------------ Reporter: g9ks157k at acme.softbase.org | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: 2.4.1 | Resolution: Keywords: lexer | ---------------------------------------+------------------------------------ Changes (by SamB): * keywords: => lexer Comment: This appears to be an infelicity in the lexer (GHC's {{{compiler/parser/HaddockLex.x}}}): {{{ { $special { strtoken $ \s -> TokSpecial (head s) } \<\<.*\>\> { strtoken $ \s -> TokPic (init $ init $ tail $ tail s) } \<.*\> { strtoken $ \s -> TokURL (init (tail s)) } \#.*\# { strtoken $ \s -> TokAName (init (tail s)) } \/ [^\/]* \/ { strtoken $ \s -> TokEmphasis (init (tail s)) } [\'\`] $ident+ [\'\`] { ident } \\ . { strtoken (TokString . tail) } "&#" $digit+ \; { strtoken $ \s -> TokString [chr (read (init (drop 2 s)))] } "&#" [xX] $hexdigit+ \; { strtoken $ \s -> case readHex (init (drop 3 s)) of [(n,_)] -> TokString [chr n] } -- allow special characters through if they don't fit one of the previous -- patterns. [\/\'\`\<\#\&\\] { strtoken TokString } [^ $special \/ \< \# \n \'\` \& \\ \]]* \n { strtoken TokString `andBegin` line } [^ $special \/ \< \# \n \'\` \& \\ \]]+ { strtoken TokString } } }}} Really, I guess the problem is that this is done in the lexer at all -- it should probably be done in {{{HaddockParse.y}}} instead. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 17 03:32:10 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 17 Feb 2009 08:32:10 -0000 Subject: [haddock] #89: character references are not recognized in emphasized text In-Reply-To: <068.fe5a61f29ee686c17df1d304b3c46dbe@projects.haskell.org> References: <068.fe5a61f29ee686c17df1d304b3c46dbe@projects.haskell.org> Message-ID: <077.75f48922ee780d299153305396bef552@projects.haskell.org> #89: character references are not recognized in emphasized text ---------------------------------------+------------------------------------ Reporter: g9ks157k at acme.softbase.org | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: 2.4.1 | Resolution: Keywords: lexer | ---------------------------------------+------------------------------------ Comment (by simonmar): one possible reason for this is so that lone '\' characters don't cause a parse error. That used to be one of the most common reasons for accidental parse errors in Haddock docs. If you look back through the logs you'll probably see when that change was made. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Thu Feb 19 12:37:19 2009 From: haddock at projects.haskell.org (haddock) Date: Thu, 19 Feb 2009 17:37:19 -0000 Subject: [haddock] #90: "-- ^" form docstrings after a -> Message-ID: <046.fd276c2567265aa8fb9a20f7e49a1e87@projects.haskell.org> #90: "-- ^" form docstrings after a -> -------------------+-------------------------------------------------------- Reporter: SamB | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: | Keywords: -------------------+-------------------------------------------------------- It has come to my attention that Haddock (well, GHC 6.8, at least) doesn't like it when you do this: {{{ myId :: a -> -- ^ Argument to return unchanged a myId x = x }}} -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Thu Feb 19 15:22:15 2009 From: haddock at projects.haskell.org (haddock) Date: Thu, 19 Feb 2009 20:22:15 -0000 Subject: [haddock] #90: "-- ^" form docstrings after a -> In-Reply-To: <046.fd276c2567265aa8fb9a20f7e49a1e87@projects.haskell.org> References: <046.fd276c2567265aa8fb9a20f7e49a1e87@projects.haskell.org> Message-ID: <055.902ab70ef8af125b77de90157f3be31d@projects.haskell.org> #90: "-- ^" form docstrings after a -> ------------------------+--------------------------------------------------- Reporter: SamB | Owner: Type: enhancement | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by waern): * type: defect => enhancement Comment: Yes, this is, I think, something that was never supported by Haddock. Not sure it should be, either. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Thu Feb 19 22:47:20 2009 From: haddock at projects.haskell.org (haddock) Date: Fri, 20 Feb 2009 03:47:20 -0000 Subject: [haddock] #90: "-- ^" form docstrings after a -> In-Reply-To: <046.fd276c2567265aa8fb9a20f7e49a1e87@projects.haskell.org> References: <046.fd276c2567265aa8fb9a20f7e49a1e87@projects.haskell.org> Message-ID: <055.25001273d2d3ba2e9e06de5d929ec6bc@projects.haskell.org> #90: "-- ^" form docstrings after a -> ------------------------+--------------------------------------------------- Reporter: SamB | Owner: Type: enhancement | Status: new Priority: major | Milestone: 2.5.0 Version: | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by SamB): Perhaps not. I may be taking that "different coding styles" thing a bit far. (*I* never write code like that myself, I just tried to haddockize some previously-written code that way.) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From mail at joachim-breitner.de Fri Feb 20 05:30:18 2009 From: mail at joachim-breitner.de (Joachim Breitner) Date: Fri, 20 Feb 2009 11:30:18 +0100 Subject: darcs patch: Typo in comment Message-ID: Hi, just stumbeld over this. You see, darcs makes it too easy to submit patches :-) Greetings, Joachim Fri Feb 20 11:29:43 CET 2009 Joachim Breitner * Typo in comment -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 19468 bytes Desc: A darcs patch for your repository! Url : http://projects.haskell.org/pipermail/haddock/attachments/20090220/80497258/attachment.bin From david.waern at gmail.com Fri Feb 20 07:08:41 2009 From: david.waern at gmail.com (David Waern) Date: Fri, 20 Feb 2009 13:08:41 +0100 Subject: darcs patch: Typo in comment In-Reply-To: References: Message-ID: Thanks! :) David 2009/2/20 Joachim Breitner : > Hi, > > just stumbeld over this. You see, darcs makes it too easy to submit patches :-) > > Greetings, > Joachim > > Fri Feb 20 11:29:43 CET 2009 Joachim Breitner > * Typo in comment > > > _______________________________________________ > Haddock mailing list > Haddock at projects.haskell.org > http://projects.haskell.org/cgi-bin/mailman/listinfo/haddock > > From haddock at projects.haskell.org Fri Feb 20 13:17:21 2009 From: haddock at projects.haskell.org (haddock) Date: Fri, 20 Feb 2009 18:17:21 -0000 Subject: [haddock] #91: gzrkqwpa Message-ID: <051.e26bed5e2447a4e421a1a330e21f8740@projects.haskell.org> #91: gzrkqwpa -----------------------+---------------------------------------------------- Reporter: anonymous | Type: enhancement Status: new | Priority: critical Milestone: 2.2.0 | Version: 2.5.0 Keywords: untmskjl | -----------------------+---------------------------------------------------- http://www.gaiougictpiblqwf.com [url=http://www.hangmgicuntclakq.com] site2[/url] site3 site4 [url="http://www.laibugicpveglmfp.com"] site5[/url] [LINK http://www.maagmgicsyvhlvox.com] site6[/LINK] agqjc -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Fri Feb 20 19:22:03 2009 From: haddock at projects.haskell.org (haddock) Date: Sat, 21 Feb 2009 00:22:03 -0000 Subject: [haddock] #91: Complexity annotations Message-ID: <062.0ad407499f6b982717172cf8e6f7c9b4@projects.haskell.org> #91: Complexity annotations ----------------------------------+----------------------------------------- Reporter: pumpkingod at gmail.com | Type: enhancement Status: new | Priority: minor Milestone: 2.5.0 | Version: Keywords: | ----------------------------------+----------------------------------------- It would be nice to be able to annotate certain functions with their time (maybe even space, if appropriate) complexity, and to have it appear in a distinctive place in the generated HTML. Currently some libraries write it at the beginning of the textual documentation of each function, which works, but it would be nice to have a more structured approach to this. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 22 07:44:10 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 22 Feb 2009 12:44:10 -0000 Subject: [haddock] #83: Better parse error messages when parsing the contents of Haddock comments In-Reply-To: <047.9addd1b8330ce3cc77af7598d273d1e6@projects.haskell.org> References: <047.9addd1b8330ce3cc77af7598d273d1e6@projects.haskell.org> Message-ID: <056.6c1e505544fc32ab83fd358cad3a5259@projects.haskell.org> #83: Better parse error messages when parsing the contents of Haddock comments ------------------------+--------------------------------------------------- Reporter: waern | Owner: Type: enhancement | Status: new Priority: major | Milestone: 2.6.0 Version: 2.4.1 | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by duncan): Just having file names and line numbers would be good. For example I got this error: {{{ haddock: parse error in doc string }}} Nothing else. No idea what is wrong, not even sure what file to look in. Turns out it was due to this: {{{ module Foo ( -- * some top level section name something, -- ** somethingElse, ) where }}} So it was just that I'd not filled in the subsection name yet. I presume that if there had been an error in the markup within that subsection name that it would have shown me the full thing. However since the problem was that it was blank, showing me the blank markup is rather confusing. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sun Feb 22 10:36:47 2009 From: haddock at projects.haskell.org (haddock) Date: Sun, 22 Feb 2009 15:36:47 -0000 Subject: [haddock] #13: Module references in doc strings are always assumed to be in the current package In-Reply-To: <047.7ee8653ee4e1d39bc47cc3f38f7c13cf@projects.haskell.org> References: <047.7ee8653ee4e1d39bc47cc3f38f7c13cf@projects.haskell.org> Message-ID: <056.66f88922126837e0caa68cb24bad4384@projects.haskell.org> #13: Module references in doc strings are always assumed to be in the current package -------------------+-------------------------------------------------------- Reporter: waern | Owner: Type: defect | Status: new Priority: major | Milestone: 2.4.2 Version: 0.x | Resolution: Keywords: | -------------------+-------------------------------------------------------- Comment (by duncan): A harder case is when a package refers to modules from another package that it does not even depend on. For example my `tar` package refers to modules from the `zlib` and `bzlib` packages. This is because it is showing examples of how to use the `tar` code to handle compressed `.tar.gz` files. It's not reasonable in this context to expect haddock to resolve the names, since they are certainly not in scope (and need not even be installed). I suggest that in such odd circumstances we allow fully package-qualified names. GHC uses the convention that fully package-qualified names use the `:` as a separator. For example I would use something like: {{{ -- | Tar files are commonly used in conjuction with gzip compression, -- as in \"@.tar.gz@\" or \"@.tar.bz2@\" files. This module does not -- directly handle compressed tar files however they can be handled -- easily by composing functions from this module and the modules -- "zlib:Codec.Compression.GZip" or "bzlib:Codec.Compression.BZip". }}} What makes this harder though is that we do not know which version of those packages to link to. We could just take it literally and hope that the unversioned url points to the latest version or something. We could allow (but probably discourage) versioned fully qualified links like: {{{ -- "zlib-0.5.0.0:Codec.Compression.GZip" or -- "bzlib-0.5.0.0:Codec.Compression.BZip". }}} So from haddock's point of view these could just be the package name, which may or may not include a version. The http link we construct would follow literally the given package name (including version if given). -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Mon Feb 23 00:50:41 2009 From: haddock at projects.haskell.org (haddock) Date: Mon, 23 Feb 2009 05:50:41 -0000 Subject: [haddock] #92: fungzsml Message-ID: <051.472859eb47ec851306f0f068656fc586@projects.haskell.org> #92: fungzsml -----------------------+---------------------------------------------------- Reporter: anonymous | Type: enhancement Status: new | Priority: critical Milestone: 2.2.0 | Version: 2.5.0 Keywords: fjcekqsy | -----------------------+---------------------------------------------------- http://tehniks.com RESERVED PRINTER fyqwcib [url=http://searchadultonly.com]ADULT[/url] ... drugs .. pills [url="http://vipmedianews.com"]news [/url] ; [LINK http://rapidpumps.com]pump[/LINK] (!) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 24 15:30:17 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 24 Feb 2009 20:30:17 -0000 Subject: [haddock] #13: Module references in doc strings are always assumed to be in the current package In-Reply-To: <047.7ee8653ee4e1d39bc47cc3f38f7c13cf@projects.haskell.org> References: <047.7ee8653ee4e1d39bc47cc3f38f7c13cf@projects.haskell.org> Message-ID: <056.74cfb3fff63ae67ebc583cece3c0d185@projects.haskell.org> #13: Module references in doc strings are always assumed to be in the current package -------------------+-------------------------------------------------------- Reporter: waern | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: 0.x | Resolution: Keywords: | -------------------+-------------------------------------------------------- Changes (by waern): * milestone: 2.4.2 => 2.5.0 -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 24 15:37:20 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 24 Feb 2009 20:37:20 -0000 Subject: [haddock] #78: Quoting full qualified names to refer to entities that are not in scope don't work. In-Reply-To: <062.105cccb174f04b4756819e02eee78903@projects.haskell.org> References: <062.105cccb174f04b4756819e02eee78903@projects.haskell.org> Message-ID: <071.156be58701c119dfa044d41bd7bd0fe8@projects.haskell.org> #78: Quoting full qualified names to refer to entities that are not in scope don't work. ---------------------------------+------------------------------------------ Reporter: gsan at stillpsycho.net | Owner: Type: defect | Status: new Priority: major | Milestone: 2.4.2 Version: 2.4.1 | Resolution: Keywords: | ---------------------------------+------------------------------------------ Comment (by waern): I don't think we should support this. What if multiple modules export the same name? I think we should at least require the user to qualify the name with a module, if the name is from the same package, and otherwise perhaps require a package qualification (see #13). -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 24 15:40:24 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 24 Feb 2009 20:40:24 -0000 Subject: [haddock] #78: Quoting full qualified names to refer to entities that are not in scope don't work. In-Reply-To: <062.105cccb174f04b4756819e02eee78903@projects.haskell.org> References: <062.105cccb174f04b4756819e02eee78903@projects.haskell.org> Message-ID: <071.175ef290345c65ae7427eb46e04211a6@projects.haskell.org> #78: Quoting full qualified names to refer to entities that are not in scope don't work. ---------------------------------+------------------------------------------ Reporter: gsan at stillpsycho.net | Owner: Type: defect | Status: new Priority: major | Milestone: 2.4.2 Version: 2.4.1 | Resolution: Keywords: | ---------------------------------+------------------------------------------ Comment (by waern): Sorry, I misread the ticket and thought it was about unqualified names. So, yes, we should support this when the names are qualified like I said in my previous note :) -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 24 15:40:34 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 24 Feb 2009 20:40:34 -0000 Subject: [haddock] #78: Quoting full qualified names to refer to entities that are not in scope don't work. In-Reply-To: <062.105cccb174f04b4756819e02eee78903@projects.haskell.org> References: <062.105cccb174f04b4756819e02eee78903@projects.haskell.org> Message-ID: <071.63e567351588d21ea3d6451f93f99f89@projects.haskell.org> #78: Quoting full qualified names to refer to entities that are not in scope don't work. ---------------------------------+------------------------------------------ Reporter: gsan at stillpsycho.net | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: 2.4.1 | Resolution: Keywords: | ---------------------------------+------------------------------------------ Changes (by waern): * milestone: 2.4.2 => 2.5.0 -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Tue Feb 24 18:31:06 2009 From: haddock at projects.haskell.org (haddock) Date: Tue, 24 Feb 2009 23:31:06 -0000 Subject: [haddock] #3: feature request: record types with partially exported fields In-Reply-To: <051.87f4ac30a5f815ec0ff95a1ecd261a8f@projects.haskell.org> References: <051.87f4ac30a5f815ec0ff95a1ecd261a8f@projects.haskell.org> Message-ID: <060.86bc7a3eb3bea2a5a03e95c8513c57fd@projects.haskell.org> #3: feature request: record types with partially exported fields ------------------------+--------------------------------------------------- Reporter: avatariks | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Version: | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by duncan): * cc: duncan (added) * priority: minor => major Comment: Resetting priority. This makes the difference between the technique being usable or not. If none of the fields get documented then nobody can decipher the api. My example is the `tar` package. I have a tar `Entry` type which is a record with a number of fields. I want to export record selectors so that user can do things like: {{{ (fileEntry name content) { fileMode = executableFileMode } }}} However I do not want clients to be able to construct an Entry directly. We provide `emptyEntry` with default fields to be overridden. This lets us add new fields and guarantee that no client will break because they cannot mis-use the constructor by doing something like: {{{ Entry blah blah blah ... }}} ie use it directly and then break when I add a field. However if I do not export the constructor then the API docs do not mention any of the fields. It becomes just: {{{ data Entry Tar archive entry }}} So, how would we document a record where the constructor(s) are not exported. Well, when the constructor is exported it looks like: {{{ data Entry Tar archive entry Constructors Entry filePath :: !TarPath Path of the file or directory. fileMode :: !FileMode UNIX file mode (file permissions). ... etc }}} So how about exactly the same but omit the Constructor name: {{{ data Entry Tar archive entry Constructors filePath :: !TarPath Path of the file or directory. fileMode :: !FileMode UNIX file mode (file permissions). ... etc }}} If there were multiple constructors then that's also ok, we can keep the blocks of record names together. Just omit the constructor name div. Similarly if we do not export all record fields names, just omit that one from the listing. Rather than switching to positional constructor style as it does now. For the synopsis it displays using Haskell syntax. Here it's harder to omit the constructor and have it look sane. Still we can probably just do it anyway. One of: {{{ data Entry = { filePath :: !TarPath fileMode :: !FileMode ... } }}} {{{ data Entry = _ { filePath :: !TarPath fileMode :: !FileMode ... } }}} or {{{ data Entry { filePath :: !TarPath fileMode :: !FileMode ... } }}} Each generalises to multiple missing or exported alternative constructors: {{{ data Entry { filePath :: !TarPath fileMode :: !FileMode ... } | { blah :: Whatever } }}} -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Wed Feb 25 11:04:59 2009 From: haddock at projects.haskell.org (haddock) Date: Wed, 25 Feb 2009 16:04:59 -0000 Subject: [haddock] #92: Source links not aligned properly in Google Chrome Message-ID: <047.335e92e3e9c360b8a5964f42d0010c1c@projects.haskell.org> #92: Source links not aligned properly in Google Chrome -------------------+-------------------------------------------------------- Reporter: waern | Owner: Type: defect | Status: new Priority: minor | Milestone: 2.6.0 Version: 2.4.1 | Keywords: HTML -------------------+-------------------------------------------------------- -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Wed Feb 25 12:09:25 2009 From: haddock at projects.haskell.org (haddock) Date: Wed, 25 Feb 2009 17:09:25 -0000 Subject: [haddock] #93: Move lexing and parsing of Haddock comments into Haddock Message-ID: <047.6706548c49c3ef5ab29ddb67f49a2533@projects.haskell.org> #93: Move lexing and parsing of Haddock comments into Haddock ------------------+--------------------------------------------------------- Reporter: waern | Owner: Type: task | Status: new Priority: major | Milestone: 2.6.0 Version: 2.4.1 | Keywords: ------------------+--------------------------------------------------------- Currently, GHC does lexing and parsing of Haddock comments. This was decided so GHC could rename the Haddock comments during its renamer phase. Since it's possible to access the renaming environment from the GHC API, we could do the renaming in Haddock instead, which would enable us to move lexing and parsing of Haddock comments into Haddock. The advantage is that we don't have to do development to GHC in order to make changes to these components. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Wed Feb 25 12:10:19 2009 From: haddock at projects.haskell.org (haddock) Date: Wed, 25 Feb 2009 17:10:19 -0000 Subject: [haddock] #93: Move lexing and parsing of Haddock comments into Haddock In-Reply-To: <047.6706548c49c3ef5ab29ddb67f49a2533@projects.haskell.org> References: <047.6706548c49c3ef5ab29ddb67f49a2533@projects.haskell.org> Message-ID: <056.71a466b204d60f5e93f9d57ae3bc6def@projects.haskell.org> #93: Move lexing and parsing of Haddock comments into Haddock ------------------------+--------------------------------------------------- Reporter: waern | Owner: Type: refactoring | Status: new Priority: major | Milestone: 2.6.0 Version: 2.4.1 | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by waern): * type: task => refactoring -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Wed Feb 25 12:19:34 2009 From: haddock at projects.haskell.org (haddock) Date: Wed, 25 Feb 2009 17:19:34 -0000 Subject: [haddock] #83: Better parse error messages when parsing the contents of Haddock comments In-Reply-To: <047.9addd1b8330ce3cc77af7598d273d1e6@projects.haskell.org> References: <047.9addd1b8330ce3cc77af7598d273d1e6@projects.haskell.org> Message-ID: <056.c96d58c8f0f0fe4d3af444d4772545cd@projects.haskell.org> #83: Better parse error messages when parsing the contents of Haddock comments ------------------------+--------------------------------------------------- Reporter: waern | Owner: Type: enhancement | Status: new Priority: major | Milestone: 2.6.0 Version: 2.4.1 | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by waern): Unfortunately, it will always give you this extremely bad error message if you're using GHC >= 6.10. We have two regressions here: - We used to "show" the AST of the markup, but that was removed during the SoC project (I can't remember why, ATM). - With GHC < 6.10 we show the source location of the Haddock comment. When support for GHC 6.10 was added, an error handler was installed only around the typechecking phase, so we miss cases like this where (I think) an error is thrown during dependency chasing. I will try to fix this second regression as soon as possible (hopefully in time for 2.4.2). But we should also: - Pretty-print the Haddock comment - Give exact source location (from within the Haddock-comment). The two above enchancements should probably be done after we have moved the parser and lexer for Haddock comments from GHC back into Haddock (see #93). -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Wed Feb 25 15:34:32 2009 From: haddock at projects.haskell.org (haddock) Date: Wed, 25 Feb 2009 20:34:32 -0000 Subject: [haddock] #83: Better parse error messages when parsing the contents of Haddock comments In-Reply-To: <047.9addd1b8330ce3cc77af7598d273d1e6@projects.haskell.org> References: <047.9addd1b8330ce3cc77af7598d273d1e6@projects.haskell.org> Message-ID: <056.c4469b648a72a6bc0f3d574ed7fac13c@projects.haskell.org> #83: Better parse error messages when parsing the contents of Haddock comments ------------------------+--------------------------------------------------- Reporter: waern | Owner: Type: enhancement | Status: new Priority: major | Milestone: 2.6.0 Version: 2.4.1 | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by waern): The second regression has been remedied. We now print the file, line and column where the comment is located. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Wed Feb 25 16:45:58 2009 From: haddock at projects.haskell.org (haddock) Date: Wed, 25 Feb 2009 21:45:58 -0000 Subject: [haddock] #69: Errors with class members In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.63bad3beb3dee338d908828180de4055@projects.haskell.org> #69: Errors with class members -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: defect | Status: reopened Priority: major | Milestone: 2.4.2 Version: 2.5.0 | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by waern): * status: closed => reopened * resolution: fixed => Comment: Oops, the patch that I wrote has a bug. We give the warning message in too many cases. I will keep this ticket open until the bug has been fixed. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Fri Feb 27 08:28:48 2009 From: haddock at projects.haskell.org (haddock) Date: Fri, 27 Feb 2009 13:28:48 -0000 Subject: [haddock] #78: Quoting full qualified names to refer to entities that are not in scope don't work. In-Reply-To: <062.105cccb174f04b4756819e02eee78903@projects.haskell.org> References: <062.105cccb174f04b4756819e02eee78903@projects.haskell.org> Message-ID: <071.9b622417d56308db780abcfe18cb9cc6@projects.haskell.org> #78: Quoting full qualified names to refer to entities that are not in scope don't work. ---------------------------------+------------------------------------------ Reporter: gsan at stillpsycho.net | Owner: Type: defect | Status: new Priority: major | Milestone: 2.5.0 Version: 2.4.1 | Resolution: Keywords: | ---------------------------------+------------------------------------------ Comment (by gsan): IIRC, the documentation says that the qualified names just create a link without doing any checks. This worked in the past but I don't know since when it's broken. This is from the latest documentation: '' It is also possible to refer to entities that are not in scope in the current module, by giving the full qualified name of the entity: '' {{{ -- | The identifier 'M.T' is not in scope }}} '' If M.T is not otherwise in scope, then Haddock will simply emit a link pointing to the entity T exported from module M (without checking to see whether either M or M.T exist). '' -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Fri Feb 27 17:41:18 2009 From: haddock at projects.haskell.org (haddock) Date: Fri, 27 Feb 2009 22:41:18 -0000 Subject: [haddock] #69: Errors with class members In-Reply-To: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> References: <054.9977cef8fe2f12de4e1f7ff83cc5eafe@projects.haskell.org> Message-ID: <063.35a443399f86346ff7b861252d40b56c@projects.haskell.org> #69: Errors with class members -------------------------+-------------------------------------------------- Reporter: NeilMitchell | Owner: Type: defect | Status: closed Priority: major | Milestone: 2.4.2 Version: 2.5.0 | Resolution: fixed Keywords: | -------------------------+-------------------------------------------------- Changes (by waern): * status: reopened => closed * resolution: => fixed Comment: Fixed by this patch: {{{ Fri Feb 27 22:37:20 CET 2009 David Waern * Bug fix We tried to filter out subordinates that were already exported through their parent. This didn't work properly since we were in some cases looking at the grand-parent and not the parent. We now properly compute all the parent-child relations of a declaration, and use this information to get the parent of a subordinate. We also didn't consider record fields with multiple parents. This is now handled correctly. We don't currently support separately exported associated types. But when we do, they should be handled correctly by this process too. Also slightly improved the warning message that we give when filtering out subordinates. }}} -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Fri Feb 27 17:50:59 2009 From: haddock at projects.haskell.org (haddock) Date: Fri, 27 Feb 2009 22:50:59 -0000 Subject: [haddock] #9: Parser doesn't support doc comments on type aliases In-Reply-To: <047.952b89217804f45f0d108f31fb315873@projects.haskell.org> References: <047.952b89217804f45f0d108f31fb315873@projects.haskell.org> Message-ID: <056.95fd9fbe2f0d4d43b91cd7493042b572@projects.haskell.org> #9: Parser doesn't support doc comments on type aliases -------------------+-------------------------------------------------------- Reporter: waern | Owner: Type: defect | Status: new Priority: major | Milestone: 2.6.0 Version: 2.1.0 | Resolution: Keywords: | -------------------+-------------------------------------------------------- Changes (by waern): * milestone: => 2.6.0 -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Fri Feb 27 17:56:33 2009 From: haddock at projects.haskell.org (haddock) Date: Fri, 27 Feb 2009 22:56:33 -0000 Subject: [haddock] #10: Starting the module with -- | doc followed by a declaration doesn't parse In-Reply-To: <047.820daef19d1969a87d224c9f0e185b70@projects.haskell.org> References: <047.820daef19d1969a87d224c9f0e185b70@projects.haskell.org> Message-ID: <056.1043ff3faa4a5cbfe3b08e59c3bc877b@projects.haskell.org> #10: Starting the module with -- | doc followed by a declaration doesn't parse -------------------+-------------------------------------------------------- Reporter: waern | Owner: Type: defect | Status: new Priority: major | Milestone: _|_ Version: 0.x | Resolution: Keywords: | -------------------+-------------------------------------------------------- Changes (by waern): * milestone: => _|_ -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Fri Feb 27 17:57:01 2009 From: haddock at projects.haskell.org (haddock) Date: Fri, 27 Feb 2009 22:57:01 -0000 Subject: [haddock] #11: Top-level Haddock comments must follow the layout of declarations In-Reply-To: <047.ee6d0aa5fc138e52081629d13a62269b@projects.haskell.org> References: <047.ee6d0aa5fc138e52081629d13a62269b@projects.haskell.org> Message-ID: <056.f4ba53b3373887db706ee53923b482a7@projects.haskell.org> #11: Top-level Haddock comments must follow the layout of declarations -------------------+-------------------------------------------------------- Reporter: waern | Owner: Type: defect | Status: new Priority: major | Milestone: 2.6.0 Version: 2.1.0 | Resolution: Keywords: | -------------------+-------------------------------------------------------- Changes (by waern): * milestone: => 2.6.0 -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Fri Feb 27 17:57:51 2009 From: haddock at projects.haskell.org (haddock) Date: Fri, 27 Feb 2009 22:57:51 -0000 Subject: [haddock] #43: GADT constructors can't be documented In-Reply-To: <073.98b324db13043501cfe5c48e5323a1b4@projects.haskell.org> References: <073.98b324db13043501cfe5c48e5323a1b4@projects.haskell.org> Message-ID: <082.f01cc83094044cf943ca031149054dc0@projects.haskell.org> #43: GADT constructors can't be documented --------------------------------------------+------------------------------- Reporter: jeanphilippe.bernardy at gmail.com | Owner: Type: defect | Status: new Priority: major | Milestone: 2.6.0 Version: 2.1.0 | Resolution: Keywords: | --------------------------------------------+------------------------------- Changes (by waern): * milestone: => 2.6.0 -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Fri Feb 27 17:58:48 2009 From: haddock at projects.haskell.org (haddock) Date: Fri, 27 Feb 2009 22:58:48 -0000 Subject: [haddock] #64: Invalid syntax generated for arrow functions In-Reply-To: <075.533a8e9c4cb0eba76634051eef2775c4@projects.haskell.org> References: <075.533a8e9c4cb0eba76634051eef2775c4@projects.haskell.org> Message-ID: <084.0f55e9cc8b5a1df76fa596ea1b0c15a5@projects.haskell.org> #64: Invalid syntax generated for arrow functions ----------------------------------------------+----------------------------- Reporter: Eyal Lotem | Owner: Type: defect | Status: new Priority: major | Milestone: 2.4.2 Version: | Resolution: Keywords: | ----------------------------------------------+----------------------------- Changes (by waern): * milestone: => 2.4.2 Comment: Should work with GHC 6.10.2 -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sat Feb 28 10:39:54 2009 From: haddock at projects.haskell.org (haddock) Date: Sat, 28 Feb 2009 15:39:54 -0000 Subject: [haddock] #57: haddock doubles ^Ms In-Reply-To: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> References: <047.79a239679df53f425d8696d4193821cb@projects.haskell.org> Message-ID: <056.1760f4be5f4df6c90c6b16c358abf277@projects.haskell.org> #57: haddock doubles ^Ms -------------------+-------------------------------------------------------- Reporter: igloo | Owner: Type: defect | Status: closed Priority: major | Milestone: 2.4.2 Version: | Resolution: fixed Keywords: | -------------------+-------------------------------------------------------- Changes (by waern): * status: new => closed * resolution: => fixed Comment: The problem is that doc strings can contain CRLF line endings. Both the HTML and Hoogle backend are written with the assumption that line endings are represented by LF only (since this is the assumption taken by the Haskell String functions such as lines, unlines and even IO commands such as hPutStr which inserts CRs before LFs?). So we should let LF be our internal format and convert to it in the doc string lexer. This patch for GHC should do it: {{{ Sat Feb 28 15:53:51 CET 2009 David Waern * Filter out carriage returns in doc strings We want the internal format to contain LFs only. This makes it easier to work with the doc strings for clients of the GHC API. }}} -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sat Feb 28 10:54:54 2009 From: haddock at projects.haskell.org (haddock) Date: Sat, 28 Feb 2009 15:54:54 -0000 Subject: [haddock] #93: Move lexing and parsing of doc strings into Haddock In-Reply-To: <047.6706548c49c3ef5ab29ddb67f49a2533@projects.haskell.org> References: <047.6706548c49c3ef5ab29ddb67f49a2533@projects.haskell.org> Message-ID: <056.8dfdda86df950da1a85910f0887fda97@projects.haskell.org> #93: Move lexing and parsing of doc strings into Haddock ------------------------+--------------------------------------------------- Reporter: waern | Owner: Type: refactoring | Status: new Priority: major | Milestone: 2.6.0 Version: 2.4.1 | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by waern): * summary: Move lexing and parsing of Haddock comments into Haddock => Move lexing and parsing of doc strings into Haddock Old description: > Currently, GHC does lexing and parsing of Haddock comments. This was > decided so GHC could rename the Haddock comments during its renamer > phase. Since it's possible to access the renaming environment from the > GHC API, we could do the renaming in Haddock instead, which would enable > us to move lexing and parsing of Haddock comments into Haddock. The > advantage is that we don't have to do development to GHC in order to make > changes to these components. New description: Currently, GHC does lexing and parsing of doc strings. This was decided so GHC could rename them during its renamer phase. Since it's possible to access the renaming environment from the GHC API, we could do the renaming in Haddock instead, which would enable us to move lexing and parsing of doc strings into Haddock. The advantage is that we don't have to do development to GHC in order to make changes to these components. -- Ticket URL: haddock Haddock, The Haskell Documentation Tool From haddock at projects.haskell.org Sat Feb 28 15:24:25 2009 From: haddock at projects.haskell.org (haddock) Date: Sat, 28 Feb 2009 20:24:25 -0000 Subject: [haddock] #60: Parser fails on same-line documentation In-Reply-To: <047.261d9f16361abfc3d91541a3f464be8a@projects.haskell.org> References: <047.261d9f16361abfc3d91541a3f464be8a@projects.haskell.org> Message-ID: <056.a4eeffa445be5c9c070ec3b55396e92a@projects.haskell.org> #60: Parser fails on same-line documentation -------------------+-------------------------------------------------------- Reporter: ryani | Owner: Type: defect | Status: new Priority: major | Milestone: Version: | Resolution: Keywords: | -------------------+-------------------------------------------------------- Changes (by colin-adams): * cc: gwern0 at gmail.com (removed) * cc: colin at colina.demon.co.uk (added) * priority: minor => major -- Ticket URL: haddock Haddock, The Haskell Documentation Tool