Dear all,
(Fergus Anderson writing)
> On first impression, having just read the paper "Type restrictions for
> overloading, without restrictions, declarations or annotations",
> I don't think I like system CT very much, because I think declaring
> interfaces is very important for soft
On 21-May-1999, Nigel Perry <[EMAIL PROTECTED]> wrote:
> At 8:02 am +1000 21/5/99, Fergus Henderson wrote:
> > On 20-May-1999, S. Alexander Jacobson <[EMAIL PROTECTED]> wrote:
>
> > > For example, how does overloading interact with the module system?
> > > When you import a function from another
On 20-May-1999, Carlos Camarao de Figueiredo <[EMAIL PROTECTED]> wrote:
>
> Dear Alex Jacobson,
>
> > Does overloading mean that you don't need MPTC? One of the nice
> > things about type classes is they provide a nice way of grouping
> > related functions. Arguably, with overloading, this wor
At 8:02 am +1000 21/5/99, Fergus Henderson wrote:
> On 20-May-1999, S. Alexander Jacobson <[EMAIL PROTECTED]> wrote:
> > For example, how does overloading interact with the module system?
> > When you import a function from another module, do you need to specify a
> > type as well as a name?
>
>
On 20-May-1999, Patrick Logan <[EMAIL PROTECTED]> wrote:
> Fergus Henderson writes:
> >
> > For that kind of thing, you should use type classes and, if need be,
> > existential types.
>
> Hmm. Thanks. I misunderstood what "ad hoc polymorphism" is. I thought
> ad hoc polymorphism in the new H
I wrote:
> After all, the world's most famous text-processing
> language, Perl,represents strings as character lists too.
I thought I had read this somewhere, for example O'Reilly's "camel" book,
but I can't find the place, and Carl Witty assures me that Perl represents
strings internally in the
I am pleased to make the first public release of Edison, a library of
data structures for Haskell. See
http://www.cs.columbia.edu/~cdo/edison/
for details.
Many thanks to Ralf Hinze for solving the makefile problems that
had been plaguing me for many months!
Chris Okasaki
At 10:48 am -0300 20/5/99, Carlos Camarao de Figueiredo wrote:
> investigate (it seems a little strange to provide type inference and
> also require top-level type declarations).
Well I might disagree - I'm one of those who think type declarations help to document
the code, though I'm happy to
On 20-May-1999, S. Alexander Jacobson <[EMAIL PROTECTED]> wrote:
> The discussion of overloading seems very abstract.
> The question is really how overloading interacts with other language features.
Your questions below are all good questions.
> For example, how does overloading interact with th
On 20-May-1999, Patrick Logan <[EMAIL PROTECTED]> wrote:
> A problem that has not been fully resolved, AFAICT, in Haskell, is
> programming-in-the-large. What ad hoc polymorphism is good for in
> languages like Smalltalk, C++, etc. is to develop frameworks of large
> applications that can be exten
Fergus Henderson wrote:
> On first impression, having just read the paper "Type restrictions for
> overloading, without restrictions, declarations or annotations",
> I don't think I like system CT very much, because I think declaring
> interfaces is very important for software engineering reasons
11 matches
Mail list logo
