From: Michael Vanier <mvanier@cs.caltech.edu>
To: checker@d6.com
Cc: caml-list@inria.fr
Subject: Re: wanted features (was: Re: [Caml-list] Bigarray map & set/get (long))
Date: Fri, 26 Jul 2002 15:40:08 -0700 [thread overview]
Message-ID: <200207262240.g6QMe8715898@orchestra.cs.caltech.edu> (raw)
In-Reply-To: <4.3.2.7.2.20020726153129.02ac9100@mail.d6.com> (message from Chris Hecker on Fri, 26 Jul 2002 15:33:06 -0700)
Yes, I meant about views. Thanks. Here's a good reference:
http://citeseer.nj.nec.com/5295.html
Mike
> Date: Fri, 26 Jul 2002 15:33:06 -0700
> From: Chris Hecker <checker@d6.com>
>
> >Could you give an example? I'm a bit fuzzy on what you mean by this.
>
> By which? Views?
>
> http://www.google.com/search?q=views+pattern+matching+abstract+data+types
>
> Chris
>
>
> At 22:44 7/25/02 -0700, Michael Vanier wrote:
>
> > > Date: Thu, 25 Jul 2002 11:11:08 -0700
> > > From: Chris Hecker <checker@d6.com>
> > >
> > > [*] My current list of needed/wanted language features:
> > >
> > > 1. operator overloading/generics for making math less ugly and painful
> > > 2. module recursion
> > > 3. views for pattern matching abstract data types
> > >
> > > I added views to my want-list relatively recently (6 months ago?) as I
> > > started trying to do more interesting stuff. I can't believe the conflict
> > > between wanting to pattern match like you're supposed to in ml and wanting
> > > to abstract data types like you're supposed to in ml doesn't get more
> > > attention in the functional programming community. It seems like a
> > glaring
> > > problem, but maybe I'm missing something.
> > >
> >
> >Could you give an example? I'm a bit fuzzy on what you mean by this.
> >
> >Mike
> >-------------------
> >To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
> >Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
> >Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>
>
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-07-27 22:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 13:59 [Caml-list] Bigarray map & set/get (long) Christophe TROESTLER
2002-07-20 18:29 ` Daniel de Rauglaudre
2002-07-21 0:45 ` Oleg
2002-07-22 13:30 ` [Caml-list] Bigarray map & set/get Christophe TROESTLER
2002-07-22 9:31 ` [Caml-list] Bigarray map & set/get (long) Xavier Leroy
2002-07-22 13:03 ` [Caml-list] Bigarray map & set/get Christophe TROESTLER
2002-07-22 15:43 ` [Caml-list] Bigarray map & set/get (long) Fernando Alegre
2002-07-25 3:02 ` Chris Hecker
2002-07-25 9:30 ` Xavier Leroy
2002-07-25 18:11 ` Chris Hecker
2002-07-26 5:44 ` Michael Vanier
2002-07-26 22:33 ` wanted features (was: Re: [Caml-list] Bigarray map & set/get (long)) Chris Hecker
2002-07-26 22:40 ` Michael Vanier [this message]
2002-07-26 22:44 ` Chris Hecker
2002-07-27 0:28 ` Michael Vanier
2002-07-27 0:32 ` Chris Hecker
2002-07-27 10:53 ` Dimitri Ara
2002-07-27 12:06 ` Dimitri Ara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200207262240.g6QMe8715898@orchestra.cs.caltech.edu \
--to=mvanier@cs.caltech.edu \
--cc=caml-list@inria.fr \
--cc=checker@d6.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).