Re: The type of zip

Claus Reinke wrote: > > The problem with tuples is that each length of tuple comes as a separate > piece of *syntax* in Haskell, not built in a compositional way from tuples > of smaller length. Type classes enable meta-programming based on types, > but not based on syntax.. > > If you are happy

Re: Haskell libraries, support status, and range of applicability(was: Haskell jobs)

Mon, 24 Jul 2000 19:01:42 +0100, Claus Reinke <[EMAIL PROTECTED]> pisze: > They might download one of the libraries that looks portable, > and find it working, more or less, but with quite a few changes > that would have to be made to it, too. Then they might look for > todo-lists, release plan

Re: The type of zip

Marcin 'Qrczak' Kowalczyk: > Also I was not able to unify callN series from > (QForeign.hs). I only had a quick look at QForeign.hs, so I'm not sure whether this will help (do you really need that odd chaining of conversion functions? and why do you pass

Re: hGetChar considered harmful

Marcin Kowalczyk writes: >Sun, 23 Jul 2000 19:38:39 -0700 (PDT), Richard Uhtenwoldt <[EMAIL PROTECTED]> pisze: > >> but it would be nice for a small program fragment be able to loop over >> the contents of an input file without resorting to "catch", which is >> more awkard than most constructs. t

Re: Haskell libraries, support status, and range of applicability(was: Haskell jobs)

Jan Skibinski: > On Wed, 19 Jul 2000, Claus Reinke wrote: > > [List of some examples of library status information..] > > They are all fine and useful. But I do not see any clear > incentives for authors for doing so, apart from their > desire to make libraries perfect .. in their spare time,

Re: Precision problem

Julian Assange wrote: > Microsoft VCC once (still?) suffers from this problem. Whether > it is because it accesses random, unassigned memory locations > or because the optimiser has time thesholds, is unknown. Optimisers for Intel can produce different results on floating point because floating po

Re: The type of zip

At 06:33 PM 7/24/00 +1000, Fergus Henderson wrote: >On 24-Jul-2000, Chris Angus <[EMAIL PROTECTED]> wrote: >> Has anyone ever thought of trying to use reflection in these cases. > >Yes, I've thought of it. That is how we implement the generic >`read' and `print' in Mercury. Using reflection like

Re: The type of zip

On 24-Jul-2000, Chris Angus <[EMAIL PROTECTED]> wrote: > Has anyone ever thought of trying to use reflection in these cases. Yes, I've thought of it. That is how we implement the generic `read' and `print' in Mercury. Using reflection like this seems to be a quite powerful technique; I think th

Re: hGetChar considered harmful

Sun, 23 Jul 2000 19:38:39 -0700 (PDT), Richard Uhtenwoldt <[EMAIL PROTECTED]> pisze: > but it would be nice for a small program fragment be able to loop over > the contents of an input file without resorting to "catch", which is > more awkard than most constructs. that is easy to achieve: we > i

RE: The type of zip

A little off-topic i know but ... Has anyone ever thought of trying to use reflection in these cases. i.e. still declare the instance but have a common method which examines the arguments and dynamiclly constructs the result depending (dynamically) on the type of the argument. I have never thou