caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Florent Monnier <monnier.florent@gmail.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: Francois Berenger <berenger@riken.jp>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] SDL2 bindings, testers and feedback welcome
Date: Thu, 19 Dec 2013 02:11:25 +0100	[thread overview]
Message-ID: <CAE1DttBo=OGHn5OoyBhrB_Pir4nG3LFOowZ+mW1eE-J8=cdp5w@mail.gmail.com> (raw)
In-Reply-To: <1D227929D85A4529B3AF9CBB68358A62@erratique.ch>

2013/12/18, Daniel Bünzli wrote:
> Le mercredi, 18 décembre 2013 à 02:13, Francois Berenger a écrit :
>> Here is what I learned some time ago on this very same mailing-list;
>> at the top of some .ml file:
>>
>> module Vg = Vector_graphics
>>
>> I _love_ it.
> If you'll do that anyway, why have a long name in the first place ? Everyone
> defining his own pet names makes code less readable.

Hi Daniel,

I also like these kind of solutions like:
module Md = MyModule
let () = let foo = Md.f1 a in Md.f2 b

because I found that in practice if I use a long module name like
"MyModule" everywhere in my code the code becomes heivy. With a
diminutive (.nickname?) the code is lighter and easier to read. But
easier to read only if i know what this diminutive (/nickname?) refers
to. I found easier to find back what this diminutive refers to if it's
available at the beginning of the code file.

I'm not trying to say that this is the perfect ideal solution for
everyone, I just want to share that this is a solution that works well
for me.
And maybe someone else would find that this solution works well too
for him or her.

-- 
Florent

  reply	other threads:[~2013-12-19  1:11 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17  6:11 Daniel Bünzli
2013-12-17  7:02 ` Anthony Tavener
2013-12-17 14:17 ` Florent Monnier
2013-12-17 15:14   ` Daniel Bünzli
2013-12-18  6:54   ` Erkki Seppala
2013-12-18  8:05     ` Anthony Tavener
2013-12-18  9:24       ` Daniel Bünzli
2013-12-18  8:18     ` Florent Monnier
2013-12-22 10:01       ` Kakadu
2013-12-30 13:28         ` Vu Ngoc San
2013-12-17 17:05 ` Ashish Agarwal
2013-12-17 17:47   ` Daniel Bünzli
2013-12-17 18:57     ` Ashish Agarwal
2013-12-17 19:45       ` Anthony Tavener
2013-12-18 15:40         ` Ashish Agarwal
2013-12-18 18:02           ` Yotam Barnoy
2013-12-18 19:53             ` Daniel Bünzli
2013-12-18 22:29               ` Ashish Agarwal
2013-12-18 22:45                 ` Daniel Bünzli
2013-12-17 20:26       ` Daniel Bünzli
2013-12-18  1:13         ` Francois Berenger
2013-12-18  6:44           ` Erkki Seppala
2013-12-18  9:21           ` Daniel Bünzli
2013-12-19  1:11             ` Florent Monnier [this message]
2013-12-19  6:39       ` Florent Monnier
2013-12-17 19:29     ` Erkki Seppala
2013-12-19  5:20 ` Florent Monnier
2013-12-19  5:27   ` Florent Monnier
2013-12-19  7:13   ` Daniel Bünzli
2013-12-19 12:38     ` Florent Monnier
2014-02-12 10:43 ` Daniel Bünzli

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='CAE1DttBo=OGHn5OoyBhrB_Pir4nG3LFOowZ+mW1eE-J8=cdp5w@mail.gmail.com' \
    --to=monnier.florent@gmail.com \
    --cc=berenger@riken.jp \
    --cc=caml-list@inria.fr \
    --cc=daniel.buenzli@erratique.ch \
    /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).