From: Florent Monnier <monnier.florent@gmail.com>
To: Ashish Agarwal <agarwal1975@gmail.com>
Cc: "Daniel Bünzli" <daniel.buenzli@erratique.ch>,
"caml list" <caml-list@inria.fr>
Subject: Re: [Caml-list] SDL2 bindings, testers and feedback welcome
Date: Thu, 19 Dec 2013 07:39:18 +0100 [thread overview]
Message-ID: <CAE1DttAAXrFGBVgEbYFPu-8-KDzFrrdOKWsjAf1w-R7bTqPRng@mail.gmail.com> (raw)
In-Reply-To: <CAMu2m2KfPFUUPFmUTnqkTB0-EmETg0eQ+c50AzCk9ZMTie6Bow@mail.gmail.com>
2013/12/17, Ashish Agarwal wrote:
> On Tue, Dec 17, 2013 at 12:47 PM, Daniel Bünzli wrote:
[...]
>> I could have used Sdl but I don't like to take ownership of toplevel names
>> that are used in other settings.
>>
>
> Admirable, but if you're defining a library that binds to a C library, I
> think it is reasonable to take that name. We rarely have multiple OCaml
> libraries that bind to the same C library. In this case, the library name
> could be sdl or ocaml-sdl (or sdl2 or ocaml-sdl2). I usually don't like
> adding "ocaml-" to library names because it is silly; of course it is an
> ocaml library. However, when binding to a C library, it makes some sense to
> distinguish between the OCaml and original C libraries.
There is also another project that took the base radical name SDL2
concatenated with OCaml. The upstream of this draft just took this
name because of a lack of imagination, and also because at the
beginning he was willing to write something that would be painless to
migrate from the origine OCamlSDL. This upstream really don't mind to
rename it into something else if someone suggests a nice name.
Maybe "rsdl2" standing for "relays to SDL2" :o)
> I misspoke. What I meant is: I don't like short cryptic acronyms. They
> appear random to me because I don't know what they mean.
This is an interesting point. Since several months, I made the test to
use a localised translation which is not an acronym for talking about
"OSM" to some people in the street and in local shops, and it really
makes it easier to talk about this project then. But such a trick is
maybe not needed for a project targetting people who like cryptic
computer stuff :o)
--
Florent
next prev parent reply other threads:[~2013-12-19 6:39 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
2013-12-19 6:39 ` Florent Monnier [this message]
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=CAE1DttAAXrFGBVgEbYFPu-8-KDzFrrdOKWsjAf1w-R7bTqPRng@mail.gmail.com \
--to=monnier.florent@gmail.com \
--cc=agarwal1975@gmail.com \
--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