August 2004 - Libraries

Module names vs file path in Setup.description
by Krasimir Angelov 10 Aug '04

10 Aug '04

Thinking about package description I wonder why the "modules" field in Setup.description is defines as a set of module names, while "main-is" is defines as file path. The "c-sources" also uses list of file paths. When using the module names it is easier to determine the file names. Maybe it's better to use module names only for "exposed-modules" field. I also propose to rename "modules" to "hs-sources". In such way all fields which specify files will use the same format. Cheers, Krasimir __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail

2 2

RE: Text.PrettyPrint.HughesPJ.quotes
by Simon Marlow 06 Aug '04

06 Aug '04

On 05 August 2004 13:47, Christian Maeder wrote: > quotes :: Doc -> Doc > Wrap document in '...' > > Prelude Text.PrettyPrint.HughesPJ> quotes empty > `' > > Either the (haddock) documentation or the implementation is wrong. > Is the first sign really supposed to be a back quote? I'd like to change the implementation to use ordinary forward single quotes. The backtick is not a quotation mark - it looks ok in some fonts (eg. the X11 misc fonts), but not in others. There's an article somewhere on the web that describes why backticks should not be used as single quotes, I can probably dig it up if anyone's interested. I'm aware that GHC is a serious offender here :-) Any objections to changing this in Text.PrettyPrint.HughesPJ? Cheers, Simon

4 3

RE: dashes in cabal package names
by Simon Marlow 06 Aug '04

06 Aug '04

On 06 August 2004 12:53, Martin Sjögren wrote: >> Dashes in package names? Absolutely. I don't think you need a >> non-dash separator between the package name and the version number, >> just take the last dash in the package id as the name-version >> separator. >> >> (I really like the <pkgname>-<version> format, probably because it's >> so widespread these days). > > We-ell, there's the issue of the version tags, which use dashes as > separator. But if we disallow tags in the package-id, it shouldn't be > a problem. foo-bar-0.1.2-bar-foo is harder to understand, though. :) Grrr. Forgot about the tags. I suggest tags use an underscore separator rather than a dash. Cheers, Simon

3 2

RE: dashes in cabal package names
by Simon Marlow 06 Aug '04

06 Aug '04

On 31 July 2004 18:42, Isaac Jones wrote: > Does anyone have any objection to allowing dashes within Cabal pacakge > names? This might impact the parser for HC-PKG, but that's the way it > is now, and seems to make the most sense. > > I think the only change to HC-PKG would be to use a non-dash separator > between the package and version; we can decide exactly how to do that > at a later time. Dashes in package names? Absolutely. I don't think you need a non-dash separator between the package name and the version number, just take the last dash in the package id as the name-version separator. (I really like the <pkgname>-<version> format, probably because it's so widespread these days). Cheers, SImon

2 1

Text.PrettyPrint.HughesPJ.quotes
by Christian Maeder 05 Aug '04

05 Aug '04

quotes :: Doc -> Doc Wrap document in '...' Prelude Text.PrettyPrint.HughesPJ> quotes empty `' Either the (haddock) documentation or the implementation is wrong. Is the first sign really supposed to be a back quote? Christian

1 0

[announce] a yum/apt repository of Haskell rpm packages
by Jens Petersen 02 Aug '04

02 Aug '04

Finally I got round to setting up a apt/yum repository of Haskell packages for users of Fedora Core. See http://haskell.org/fedora/ for more details. Feedback is very welcome. Cheers, Jens ps This will replace my Haskell rpms directory on haskell.org.

1 0

Announce: Cabal 0.1 (Library Infrastructure Project)
by Isaac Jones 02 Aug '04

02 Aug '04

Much thanks to all who've made this possible :) The Haskell Cabal The Common Architecture for Building Applications and Libraries. DOWNLOAD: The Haskell Cabal has reached pre-release stage, with a 0.1 version The community should use this release to evaluate the interfaces and explore the concepts of these tools. Download the Cabal here: http://www.haskell.org/cabal/download.html BUGS: Please report bugs and wish-list items here: http://sourceforge.net/tracker/?func=add&group_id=44807&atid=440922 Or email Isaac Jones: ijones(a)syntaxpolice.org ABOUT: The Haskell Cabal is meant to be a part of a larger infrastructure for distributing, organizing, and cataloging Haskell Libraries and Tools. It is an effort to provide a framework for developers to more effectively contribute their software to the Haskell community. Specifically, the Cabal describes what a Haskell package is, how these packages interact with the language, and what Haskell implementations must to do to support packages. The Cabal also specifies some infrastructure (code) that makes it easy for tool authors to build and distribute conforming packages. The Cabal is only one contribution to the larger goal. In particular, the Cabal says nothing about more global issues such as how authors decide where in the module name space their library should live; how users can find a package they want; how orphan packages find new owners; and so on. NOTES: This release is meant to provide the community with concrete information about how the interfaces are shaping up. This release does NOT fix the interfaces, we can't promise not to break anything that relies on these interfaces. We hope that Haskell authors will try to package their software using these tools, and let us know where they fall short. MORE INFORMATION: Please see the web site for the source code, interfaces, and especially the proposal, which will serve as documentation for this release: http://www.haskell.org/cabal/

2 2