Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: John Whitington <john@coherentgraphics.co.uk>
To: Francois Berenger <francois.berenger@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] use of ";;" when teaching Ocaml
Date: Mon, 22 Jun 2015 18:53:32 +0100	[thread overview]
Message-ID: <55884B9C.9000404@coherentgraphics.co.uk> (raw)
In-Reply-To: <5588490B.3010402@inria.fr>

Hi Francois,

cat src/test.ml
---
failwith "I don't recommend this"
---

(Assuming you're not exporting main in an interface, and just want an 
error if the module is linked and its initialiser run.)

John

Francois Berenger wrote:
> On 06/22/2015 06:07 PM, Mark Shinwell wrote:
>> I've heard the argument of Gerd from various people on many occasions.
>> Personally, I don't buy it; I think the situation where the error
>> message is deficient doesn't happen very often, whereas ";;" is
>> syntactic clutter that I have to see every day (and would rather not
>> see).
>>
>> Mark
>
> I am curious.
> How do you make this file compile without ';;' in it ?
>
> # cat src/test.ml
> ---
> let main () =
> failwith "not implemented yet"
> ;;
>
> main ()
> ---
>
> I always use ';;' just for that use case.
> I really don't know if there is another way that fits a single file.
>
>> On 22 June 2015 at 16:56, Thomas Refis <thomas.refis@gmail.com> wrote:
>>> 2015-06-22 16:48 GMT+01:00 Damien Doligez <damien.doligez@inria.fr>:
>>>> Gerd has totally nailed it, and that's the reason why I always use ;;
>>>> in my code.
>>>> If we had another keyword for toplevel let (let without in) the
>>>> situation would be quite different.
>>>
>>> http://caml.inria.fr/pub/docs/manual-camlp4/manual007.html !
>>>
>>> --
>>> Caml-list mailing list. Subscription management and archives:
>>> https://sympa.inria.fr/sympa/arc/caml-list
>>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
>

-- 
John Whitington
Director, Coherent Graphics Ltd
http://www.coherentpdf.com/


  parent reply	other threads:[~2015-06-22 17:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 13:31 Alan Schmitt
2015-06-22 13:52 ` Ivan Gotovchits
2015-06-22 13:53 ` Daniil Baturin
2015-06-22 14:19 ` Gerd Stolpmann
2015-06-22 15:48   ` Damien Doligez
2015-06-22 15:56     ` Thomas Refis
2015-06-22 16:07       ` Mark Shinwell
2015-06-22 16:30         ` Gerd Stolpmann
2015-06-22 16:47           ` Mark Shinwell
2015-06-22 17:08             ` Daniel Bünzli
2015-06-22 18:56             ` Gerd Stolpmann
2015-06-22 17:18           ` Török Edwin
2015-06-22 17:42         ` Francois Berenger
2015-06-22 17:46           ` Ivan Gotovchits
2015-06-22 17:53           ` John Whitington [this message]
2015-06-22 16:07     ` Pippijn van Steenhoven
2015-06-22 16:25       ` Daniel Bünzli
2015-06-22 18:18       ` Steve Zdancewic
2015-06-22 16:42   ` Thomas Refis
2015-06-22 16:47     ` David House
2015-06-22 17:08     ` Daniil Baturin
2015-06-22 17:04 ` Daniel Bünzli
2015-06-22 23:41 ` Philippe Wang
2015-06-23  1:15   ` Kenichi Asai
2015-06-23 13:27   ` Alan Schmitt
2015-06-23 13:35     ` Ivan Gotovchits
2015-06-23 13:36       ` Ivan Gotovchits
2015-06-25 16:51     ` Philippe Wang
2015-06-29  0:12       ` Philippe Wang

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=55884B9C.9000404@coherentgraphics.co.uk \
    --to=john@coherentgraphics.co.uk \
    --cc=caml-list@inria.fr \
    --cc=francois.berenger@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