Re: The future of Haskell discussion

2001-09-15 Thread Bill Halchin
Jeff has hit the nail on the head .. thanks Jeff. You said eloquently what I was hinting at or saying very implicit (because I didn't know how to say it eloquently). The "Haskell library" seems to be contributions by individuals (who should be commended!!), but as an "industrial" programmer who w

Re: Application letters at the Haskell workshop: suggestion

2001-09-15 Thread Duncan Coutts
> On Fri, 14 Sep 2001, Mark Carroll wrote: (snip) > > simplistic (but adequate for my immediate needs, which are currently > > being served with lots of ifs and Maybes!). > > Oh - and I should add, lots of two-tuple return values which are > basically of the form (Maybe a, error details). ): > >

Re: The future of Haskell discussion

2001-09-15 Thread Pixel
"Marcin 'Qrczak' Kowalczyk" <[EMAIL PROTECTED]> writes: > Fri, 14 Sep 2001 02:09:21 -0700, Julian Seward (Intl Vendor) ><[EMAIL PROTECTED]> pisze: > > > The lack of any way to interface to C++ is a problem, IMO. > > I would love to be able to write Haskell programs using Qt > > and ultimately t

Re: Application letters at the Haskell workshop: suggestion

2001-09-15 Thread Mark Carroll
Mike - I hope you don't mind passing this to the list - but it's a great, simple explanation of a big problem with my approach. On 14 Sep 2001, Mike Gunter wrote: > The problem is not a loss of referential transparency but the > requirement that evaluation order must be specified. E.g. > what s

Re: The future of Haskell discussion

2001-09-15 Thread Manuel M. T. Chakravarty
"S. Alexander Jacobson" <[EMAIL PROTECTED]> wrote, > If the GUI is based on the IO monad, then it doesn't seem like there is > a lot of advantage to doing it in Haskell. It seems like a better > idea to use a more natural language for IO and make RPC/interproc calls > to a haskell server to get

Re: The future of Haskell discussion / GUIs

2001-09-15 Thread Manuel M. T. Chakravarty
Johannes Waldmann <[EMAIL PROTECTED]> wrote, > Manuel: > > > ... Functional GUIs like > > Fruit are from a research perspective very interesting, but > > their design is rather far from being a solved problem, > > which makes them a not very likely candidate for a standard > > that people seem t