From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 94E3A7EC6E for ; Thu, 19 Dec 2013 02:11:35 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of monnier.florent@gmail.com) identity=pra; client-ip=209.85.212.180; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="monnier.florent@gmail.com"; x-sender="monnier.florent@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of monnier.florent@gmail.com designates 209.85.212.180 as permitted sender) identity=mailfrom; client-ip=209.85.212.180; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="monnier.florent@gmail.com"; x-sender="monnier.florent@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-wi0-f180.google.com) identity=helo; client-ip=209.85.212.180; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="monnier.florent@gmail.com"; x-sender="postmaster@mail-wi0-f180.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgDAHlHslLRVdS0lGdsb2JhbABZhBe5IYEOCBYOAQEBAQcLCwkSKoIlAQEBBEABGxILAQMMBgULDS4iAREBBQEcBi6HVAEDEaUajFqDCY1tChknDWSGGBEBBQyOUzMHhDYEmBaQJxgphFg7 X-IPAS-Result: AhgDAHlHslLRVdS0lGdsb2JhbABZhBe5IYEOCBYOAQEBAQcLCwkSKoIlAQEBBEABGxILAQMMBgULDS4iAREBBQEcBi6HVAEDEaUajFqDCY1tChknDWSGGBEBBQyOUzMHhDYEmBaQJxgphFg7 X-IronPort-AV: E=Sophos;i="4.95,510,1384297200"; d="scan'208";a="41642313" Received: from mail-wi0-f180.google.com ([209.85.212.180]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 19 Dec 2013 02:11:26 +0100 Received: by mail-wi0-f180.google.com with SMTP id hm19so1485993wib.7 for ; Wed, 18 Dec 2013 17:11:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=1F4yZYjGf9YMbKc6vF9WKFMC03ZgMROzF5NUSV/LHbs=; b=c+BXtgINqZWYwTLGpxfaW0z2qcml04LmdIMRhoJHxblGMVvuCd23wnCGcMXKI2tdoW 2ACzVsmDmvIXwmIY032AiqXBPeCELgOUPD42XzeNl+7xuPdIYk2hKnLI+ZaUo2s9tUtr lp0yrmhYP+idAPtubmlbJSKkLqdfsRpyWb3qUCzDiD1kIB+gajo/NR5XxypD7Ah+n9e9 oOjuQW6GlpLIUZpkhhUHtSV4l6mJ3r45Sz+Sy40NokDg8SQDCMcnO+HymyP2FSREHXFY fW1NRR2SWhvnxbNs4VgpGgkof44LYry964Ft2h8ZxO041UMfQvbnl/bGMuw2j/g9+vir Qb+Q== MIME-Version: 1.0 X-Received: by 10.180.207.239 with SMTP id lz15mr385940wic.28.1387415485770; Wed, 18 Dec 2013 17:11:25 -0800 (PST) Received: by 10.194.77.110 with HTTP; Wed, 18 Dec 2013 17:11:25 -0800 (PST) In-Reply-To: <1D227929D85A4529B3AF9CBB68358A62@erratique.ch> References: <4DDEBB7487B641C0834F09D522EA9918@erratique.ch> <1C9496037B6149EC970D65C3BFA490F7@erratique.ch> <52B0F6A5.9060605@riken.jp> <1D227929D85A4529B3AF9CBB68358A62@erratique.ch> Date: Thu, 19 Dec 2013 02:11:25 +0100 Message-ID: From: Florent Monnier To: =?ISO-8859-1?Q?Daniel_B=FCnzli?= Cc: Francois Berenger , caml-list Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Validation-by: monnier.florent@gmail.com Subject: Re: [Caml-list] SDL2 bindings, testers and feedback welcome 2013/12/18, Daniel B=FCnzli wrote: > Le mercredi, 18 d=E9cembre 2013 =E0 02:13, Francois Berenger a =E9crit : >> Here is what I learned some time ago on this very same mailing-list; >> at the top of some .ml file: >> >> module Vg =3D Vector_graphics >> >> I _love_ it. > If you'll do that anyway, why have a long name in the first place ? Every= one > defining his own pet names makes code less readable. Hi Daniel, I also like these kind of solutions like: module Md =3D MyModule let () =3D let foo =3D 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. --=20 Florent