[Haskell] Haskell DB bindings (was Re: ANN: HDBC (Haskell Database Connectivity)

2006-01-09 Thread Tim Docker
[EMAIL PROTECTED] wrote: > Incidentally, the difficulty with finalizers was precisely the > argument for using enumerators rather than cursors in database > APIs. Takusen has implemented that idea; takusen currently supports > Sqlite, PostgreSQL and Oracle, has a test suite. Its performance test >

[Haskell] Re: ANN: HDBC (Haskell Database Connectivity)

2006-01-09 Thread oleg
Axel Simon wrote, in response to Keean Schupke > > dbConnectWith :: DbName -> (DbHandle -> IO Result) -> Result > > dbConnectWith name workFn = do > > handle <- dbConnectTo name > > workFn handle `finally` dbDisconnect handle > > > > In this way you avoid finalizers... and everthing is sa

Re: [Haskell] Re: License for haskell.org content

2006-01-09 Thread Jan-Willem Maessen
On Jan 9, 2006, at 7:19 AM, Simon Marlow wrote: Chris Kuklewicz wrote: == Conclusion It is not possible to borrow text from a GFDL'd manual and incorporate it in any free software program whatsoever. This is not a mere license incompatibility. It's not just that the GFDL is i

Re: [Haskell] haskell.org Public Domain

2006-01-09 Thread ajb
G'day all. Quoting Ashley Yakeley <[EMAIL PROTECTED]>: > Does anyone have any objections to putting everything in the public > domain? No, with the proviso that individual page authors can override that on the page itself. There is a disincentive for authors to do this, because their material m

Re: [Haskell] Re: License for haskell.org content

2006-01-09 Thread ajb
G'day all. Quoting Simon Marlow <[EMAIL PROTECTED]>: > I agree - can we please use BSD or public domain? Creative Commons "by" might be an appropriate alternative: http://creativecommons.org/licenses/by/2.5/ Cheers, Andrew Bromage ___ Haskell mai

Re: [Haskell] Re: License for haskell.org content

2006-01-09 Thread Jean-Philippe Bernardy
We could also use multi licensing. A possibility is to have, by default, everything licensed at the same time under BSD, CC, FDL and GPL. (For those who wonder, this suggestion is serious /and/ sarcastic at the same time) Cheers, JP. On 1/9/06, Ian Lynagh <[EMAIL PROTECTED]> wrote: > On Sun, Jan

[Haskell] AMAST 2006 2nd Call for Papers

2006-01-09 Thread Varmo Vene
SECOND CALL FOR PAPERS 11th International Conference on Algebraic Methodology and Software Technology, AMAST '06 colocated with MPC '06 Kuressaare, Estonia, 5-8 July 2006 http://cs.ioc.ee/mpc

Re: [Haskell] Re: haskell.org Public Domain

2006-01-09 Thread Eric Kow
Whatever the Haskell community end up deciding, I would like to point out that the Wikibooks project uses the GFDL. What would greatly simplify us wikibookians using content from the Haskell wiki are GFDL-friendly terms, that is, one of: public domain GFDL creative commons [by][sa] - that's

[Haskell] Re: New look for haskell.org: MediaWiki

2006-01-09 Thread Ashley Yakeley
Sebastian Sylvan wrote: Is there a way to typeset Haskell syntax yet? Not yet, but someone could write an extension to do that... -- Ashley Yakeley ___ Haskell mailing list Haskell@haskell.org

[Haskell] ANN: hdbc-odbc

2006-01-09 Thread John Goerzen
I am pleased to be able to announce the first version of hdbc-odbc, the ODBC backend for HDBC. With this driver, you can use HDBC to connect to any database for which ODBC drivers exist, including such databases as MySQL, Oracle, MS SQL Server, etc. I have tested it against PostgreSQL and would a

Re: [Haskell] Re: License for haskell.org content

2006-01-09 Thread Ian Lynagh
On Sun, Jan 08, 2006 at 10:16:45PM -0800, Ashley Yakeley wrote: > In article <[EMAIL PROTECTED]>, > Ian Lynagh <[EMAIL PROTECTED]> wrote: > > > Why not use the GPL, then? > > > > FWIW, the GFDL is considered non-free by Debian[1], so that would mean > > any documentation or anything derived from

[Haskell] Re: haskell.org Public Domain

2006-01-09 Thread Ashley Yakeley
Cale Gibbard wrote: As long as that's just the default and not required of course. No, all contributions would be in the public domain. It might be nice to at least include some disclaimers of warranty. Good idea. -- Ashley Yakeley ___ Haskell

Re: [Haskell] haskell.org Public Domain

2006-01-09 Thread Glynn Clements
Ashley Yakeley wrote: > > Sounds like a stupid idea? Thought so. A wiki should be public domain, > > plain and simple. (Put contributions with a different license somewhere > > else and link to them. No big deal.) > > There seems to be a consensus for public domain both here and on the > wi

Re: [Haskell] haskell.org Public Domain

2006-01-09 Thread Cale Gibbard
On 09/01/06, Ashley Yakeley <[EMAIL PROTECTED]> wrote: > In article <[EMAIL PROTECTED]>, > Udo Stenzel <[EMAIL PROTECTED]> wrote: > > > Sounds like a stupid idea? Thought so. A wiki should be public domain, > > plain and simple. (Put contributions with a different license somewhere > > else and

[Haskell] MonadPlus vs. Monoid

2006-01-09 Thread Twan van Laarhoven
I was wondering, in the MonadPlus documentation it says that: * mzero is the identity of mplus (and some extra conditions) * mplus is an associative operation While for Monoid we have: * mempty is identity of mappend * mappend is an associative operation MonadPlus is of course a 'stronger

[Haskell] haskell.org Public Domain

2006-01-09 Thread Ashley Yakeley
In article <[EMAIL PROTECTED]>, Udo Stenzel <[EMAIL PROTECTED]> wrote: > Sounds like a stupid idea? Thought so. A wiki should be public domain, > plain and simple. (Put contributions with a different license somewhere > else and link to them. No big deal.) There seems to be a consensus for p

Re: [Haskell] New look for haskell.org: MediaWiki (now: Drupal)

2006-01-09 Thread John Peterson
The reason that MediaWiki was installed on haskell.org is that people that know how to install and use MediaWiki (Ashley and others) volunteered to do all the work. If we want to move up to Drupal we need someone that is willing to install, maintain, and transfer content. If this is something you

Re: [Haskell] Re: License for haskell.org content

2006-01-09 Thread Udo Stenzel
Ketil Malde wrote: > Another option is the Open Publication License, which requires > acknowledgement (but little else). ...which would mean that whenever you rearrange something inside the wiki, you'd have to drag signatures around (and god forbid you accidentally drop a single one). The only wa

Re: [Haskell] New look for haskell.org: MediaWiki

2006-01-09 Thread Gour
On Sun, 2006-01-08 at 19:52 -0500, John Peterson wrote: > This isn't a completely "done deal" - there is still time to object to > the whole thing or make suggestions. Nothing will be visible to the > outside world until we make the switch later. But I believe this will > result in a much better

Re: [Haskell] Re: License for haskell.org content

2006-01-09 Thread Ketil Malde
Simon Marlow <[EMAIL PROTECTED]> writes: >> Thus defaulting the FDL for all wiki content, including code, is a >> very bad idea. > I agree - can we please use BSD or public domain? Another option is the Open Publication License, which requires acknowledgement (but little else). Anyway, I think

Re: [Haskell] New look for haskell.org: MediaWiki

2006-01-09 Thread Duncan Coutts
On Sun, 2006-01-08 at 21:12 -0500, John Peterson wrote: > >> wiki is under the GNU FDL so the licenses are not necessarily > >> compatible. > > >As far as I understand, this means that if I see a sample of code on > >the haskell wiki, and just want to "steal" it for my project, I'm not > >allowed

[Haskell] Re: License for haskell.org content

2006-01-09 Thread Simon Marlow
Chris Kuklewicz wrote: == Conclusion It is not possible to borrow text from a GFDL'd manual and incorporate it in any free software program whatsoever. This is not a mere license incompatibility. It's not just that the GFDL is incompatible with this or that free software license:

Re: [Haskell] New look for haskell.org: MediaWiki

2006-01-09 Thread Sebastian Sylvan
On 1/9/06, John Peterson <[EMAIL PROTECTED]> wrote: > As everyone has noticed during the "making Haskell more open" > discussion, MediaWiki was suggested as a better wiki technology for > haskell.org. Ashley Yakeley has generously installed MediaWiki and we > would like to migrate the main pages o

Re: [Haskell] New look for haskell.org: MediaWiki

2006-01-09 Thread Sebastian Sylvan
On 1/9/06, Anders Höckersten <[EMAIL PROTECTED]> wrote: > sön 2006-01-08 klockan 21:12 -0500 skrev John Peterson: > > >> wiki is under the GNU FDL so the licenses are not necessarily > > >> compatible. > > > > >As far as I understand, this means that if I see a sample of code on > > >the haskell wi

Re: [Haskell] Re: ANN: HDBC (Haskell Database Connectivity)

2006-01-09 Thread Axel Simon
On Mon, 2006-01-09 at 11:33 +0100, Benjamin Franksen wrote: > On Monday 09 January 2006 10:03, Axel Simon wrote: > > On Sun, 2006-01-08 at 14:51 +, Keean Schupke wrote: > > > My solution to this when developing a database library for my own > > > use was to define the API > > > in a bracket not

Re: [Haskell] License for haskell.org content

2006-01-09 Thread Chris Kuklewicz
I have appended the relevant conclusion Ian Lynagh wrote: > On Sun, Jan 08, 2006 at 09:31:16PM -0500, John Peterson wrote: > >>I believe the scenario that the FDL addresses is that someone >>(probably Paul Hudak!) "borrows" massive amounts of stuff from the wiki, >>adds his own good stuff, and th

[Haskell] modern arrays library

2006-01-09 Thread Bulat Ziganshin
Hello i just published the following text at the http://haskell.org/haskellwiki/Arrays Haskell'98 supports just one array constructor type, namely Array (see http://haskell.org/onlinereport/array.html). It creates immutable boxed arrays. "Immutable" means that these arrays, like any other pure

Re: [Haskell] Re: ANN: HDBC (Haskell Database Connectivity)

2006-01-09 Thread Benjamin Franksen
On Monday 09 January 2006 10:03, Axel Simon wrote: > On Sun, 2006-01-08 at 14:51 +, Keean Schupke wrote: > > My solution to this when developing a database library for my own > > use was to define the API > > in a bracket notation style, and only provide safe functions. The > > idea is that the

Re: [Haskell] Re: ANN: HDBC (Haskell Database Connectivity)

2006-01-09 Thread Axel Simon
Keean et al, On Sun, 2006-01-08 at 14:51 +, Keean Schupke wrote: > My solution to this when developing a database library for my own use > was to define the API > in a bracket notation style, and only provide safe functions. The idea > is that the function obtains the resource, calls a funct