Three patches for cabal

Simon Peyton-Jones simonpj at microsoft.com
Fri Jun 5 10:02:21 EDT 2009


Since there has been little comment on this, my preliminary conclusion is that no one cares much what the flag is called. So I've left the flag unchanged, but make the manual mention it in the right place.

If pressure builds to change the flag name, I'm happy to do so.

Simon

| -----Original Message-----
| From: Duncan Coutts [mailto:duncan.coutts at worc.ox.ac.uk]
| Sent: 05 June 2009 01:31
| To: Simon Peyton-Jones
| Cc: Max Bolingbroke; Niklas Broberg; GHC-users; Haskell Libraries
| Subject: RE: Three patches for cabal
|
| On Thu, 2009-06-04 at 08:43 +0100, Simon Peyton-Jones wrote:
| > I'd be quite happy to rename the flag to GeneralisedisedListComp, and
| > clarify the user manual.  Would that suit everyone?
| >
| > I suppose the alternative is to leave it as TransformListComp, and
| > document that fact.  But I rather agree that GeneralisedListComp fits
| > the literature better.
|
| Looking at the paper, it doesn't really give it any specific name.
| Perhaps is a good thing because we can change the ghc user guide
| relatively easily, but not published papers.
|
| I appreciate Max's point that GeneralisedListComp is a bit vague, though
| TransformListComp doesn't really speak to me. I would not (and did not)
| guess it has any relation to the extension in question. My only other
| suggestion is QueryListComp or GeneralisedQueryListComp (bikeshed
| dangers approaching...).
|
| The main point is that the docs and the extension name should be
| consistent (and should refer to each other).
|
| Duncan
|



More information about the Glasgow-haskell-users mailing list