From: Emmanuel Dieul <emmanuel.dieul@free.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Some obsolete constructions ?
Date: Fri, 30 Apr 2010 22:36:14 +0200 [thread overview]
Message-ID: <4BDB3F3E.9030603@free.fr> (raw)
In-Reply-To: <4BDAE6A2.1060902@frisch.fr>
Le 30/04/2010 16:18, Alain Frisch a écrit :
> On 04/30/2010 03:23 PM, Emmanuel Dieul wrote:
>> - Pcf_let : a let construction as a class field ?
>
> AFAIK, this one is obsolete.
>
>> - Pexp_letmodule : ?
>
> let module L = List in ();;
>
>> - Pexp_override : an override expression ?
>
> object(this) method m = {< >} end;;
>
>> - Ppat_type : a type pattern matching ?
>
> type t = [`A];;
> fun #t -> ();;
>
>> - Rinherit : an inherit row field ?
>
> type t = [`A];;
> type s = [t | `B];;
>
>
> -- Alain
>
>
Great ! This completes my knowledge of ocaml constructions !...
Thanks !
prev parent reply other threads:[~2010-04-30 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 13:23 Emmanuel Dieul
2010-04-30 14:18 ` [Caml-list] " Alain Frisch
2010-04-30 20:36 ` Emmanuel Dieul [this message]
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=4BDB3F3E.9030603@free.fr \
--to=emmanuel.dieul@free.fr \
--cc=caml-list@inria.fr \
/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).