From: Berke Durak <berke.durak@exalead.com>
To: Edgar Friendly <thelema314@gmail.com>
Cc: "Tiphaine.Turpin" <Tiphaine.Turpin@free.fr>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] OO programming
Date: Mon, 25 Feb 2008 17:02:22 +0100 [thread overview]
Message-ID: <47C2E68E.2020401@exalead.com> (raw)
In-Reply-To: <47C2E369.9080206@gmail.com>
Edgar Friendly a écrit :
> Tiphaine.Turpin wrote:
>>> or they are required by the GUI
>>> layer), and that OCaml has now way to seperate method/function
>>> declaration and type declaration (unless one uses a mli file, which is
>>> again inconvenient because it splits information that belongs together
>>> into two complete different places). I'd really appreciate it if one
>>> could just mix "val" type declcarations with "let" or "method" code
>>> declarations.
>>>
>> I don't understand what you want here.
>
> I read him as asking for .ml files to contain what .mli files now
> contain - i.e. method/function declarations
>
> Example - string_annex.ml:
>
> val init: int -> (int -> char) -> string
>
> let init n f =
> let s = make n (f 0) in
> for i=1 to n-1 do
> set s i (f i);
> done;
> s
>
>
> OCaml doesn't permit this at the moment because val statements go in
> .mli files (or in sig blocks) only.
>
Yes that could be nice but it's no biggie IMHO.
let init n f =
let s = make n (f 0) in
for i=1 to n-1 do
set s i (f i);
done;
s
let init : int -> (int -> char) -> string = init
--
Berke DURAK
next prev parent reply other threads:[~2008-02-25 16:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 9:31 Tiphaine Turpin
2008-02-21 9:42 ` [Caml-list] " Erik de Castro Lopo
2008-02-21 13:38 ` Remi Vanicat
2008-02-24 16:33 ` [Caml-list] " Dirk Thierbach
2008-02-25 9:23 ` Tiphaine.Turpin
2008-02-25 15:48 ` Edgar Friendly
2008-02-25 16:02 ` Berke Durak [this message]
2008-02-25 20:12 ` Dirk Thierbach
2008-02-25 20:51 ` Tiphaine.Turpin
2008-02-25 23:03 ` Dirk Thierbach
2008-02-25 20:10 ` Dirk Thierbach
2008-02-25 21:49 ` Tiphaine.Turpin
2008-02-25 23:07 ` Dirk Thierbach
2008-02-29 14:22 ` Tiphaine.Turpin
2008-02-26 6:17 ` Jacques Garrigue
2008-02-26 9:36 ` Julien Signoles
2008-02-27 0:25 ` Tiphaine.Turpin
2008-02-27 1:37 ` Jacques Garrigue
2008-02-28 8:34 ` Keiko Nakata
2008-02-28 13:30 ` Andrej Bauer
2008-02-28 15:18 ` Keiko Nakata
2008-02-28 16:02 ` Edgar Friendly
2008-02-29 14:35 ` Tiphaine.Turpin
2008-02-29 15:58 ` Keiko Nakata
2008-03-03 9:40 ` Tiphaine.Turpin
2008-03-03 10:20 ` Jacques Garrigue
2008-03-03 10:30 ` Tiphaine.Turpin
2008-03-03 15:18 ` Keiko Nakata
2008-03-03 19:25 ` Tiphaine Turpin
2008-03-04 14:00 ` Keiko Nakata
2008-02-27 7:40 ` Dirk Thierbach
2008-02-27 14:04 ` Tiphaine.Turpin
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=47C2E68E.2020401@exalead.com \
--to=berke.durak@exalead.com \
--cc=Tiphaine.Turpin@free.fr \
--cc=caml-list@yquem.inria.fr \
--cc=thelema314@gmail.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