[Haskell-cafe] Oracle + Haskell advice?

2005-08-17 Thread Brian Strand

Hello,

I'm thinking about (re)writing some perl code in Haskell (for performance and 
correctness reasons).  Has anyone done much with Oracle and Haskell?  So far 
I've gotten takusen (http://cvs.sf.net/viewcvs.py/haskell-libs/libs/takusen/) 
to compile and run on my Suse 9.3 x86-64 box against Oracle 10.1.  If this 
pans out the production environment is a bunch of mid-size (4gb+ mem, 1tb+ 
disk) Oracle boxes typically processing millions of rows per day.


Before I wade in too deep, I'm wondering if anyone has done much "business 
app" programming with Haskell (where "business app" is rather fuzzily defined 
as database access, web UIs, interfacing with various systems over ip, etc.). 
 Does anyone have any advice?  eg "don't go there" or "works great!" or "try 
OCaml" :) .


Thanks,
Brian

___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


Re: [Haskell-cafe] Re: [Haskell] pros and cons of static typing andside effects ?

2005-08-17 Thread Sebastian Sylvan
On 8/17/05, Ralf Lammel <[EMAIL PROTECTED]> wrote:
> I don't even want this feature. :-)
> The point being that datatype declarations, *as such*, are explicit
> anyhow.
> Why bother about the explicit quantifiers then?
> Of course, in a language with inferred datatypes I would mind.
> That's an interesting question!
> 
> I also wouldn't (yet?!) support this feature request
> because we will still confuse beginners, but that's just my feeling.

Really? I don't think that would confuse beginners at all. They
wouldn't care about the theory behind it they'd just think along the
lines of "internal and external type variables" or something like
that.

Anyway, it's not really needed if GADT becomes the norm, since that
syntax is quite understandable anyway.

-- 
Sebastian Sylvan
+46(0)736-818655
UIN: 44640862
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


RE: [Haskell-cafe] Re: [Haskell] pros and cons of static typing andside effects ?

2005-08-17 Thread Ralf Lammel
I don't even want this feature. :-)
The point being that datatype declarations, *as such*, are explicit
anyhow.
Why bother about the explicit quantifiers then?
Of course, in a language with inferred datatypes I would mind.
That's an interesting question!

I also wouldn't (yet?!) support this feature request
because we will still confuse beginners, but that's just my feeling.

Ralf

> -Original Message-
> From: Stefan Holdermans [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 16, 2005 11:48 PM
> To: Ralf Lammel
> Cc: haskell-cafe@haskell.org; Benjamin Franksen
> Subject: Re: [Haskell-cafe] Re: [Haskell] pros and cons of static
typing
> andside effects ?
> 
> Ralf,
> 
> > Technically this is trivial it seems. I think that some people
> > consider this proposal a problem because typos (misspelled type
> > parameters) immediately lead to the accidental exploration of a more
> > advanced type-system feature and correspondingly more involved error
> > messages. Of course, the type checker could perhaps consider adding
> > "Did you really mean to ...?".
> 
> Well, okay, but as soon as the type checker starts to asking these
> questions, I would immediately start adding the explicit quantifiers,
> just to get rid of those annoying warning messages. ;) So one would we
> also need to be able to control the behaviour of the type checker with
> respect to these warnings by means of a compiler flag like
> "fno-warn-on-implicit-existential-quantification". All of this is, of
> course, still trivial. :)
> 
> Have we thought about it enough to make it a feature request?
> 
> Regards,
> 
> Stefan

___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe


[Haskell-cafe] embedding prolog in haskell.

2005-08-17 Thread Keean Schupke
Does anyone know if the source code for the embedded prolog (by Silvija 
Seres & Michael Spivey) is available for download from anywhere? I have 
read the paper and found some of the types are wrong, some critical 
definitions are missing, and the definition of unify is missing.


   Regards,
   Keean.
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe