From: Yotam Barnoy <yotambarnoy@gmail.com>
To: Ashish Agarwal <agarwal1975@gmail.com>
Cc: "Anthony Tavener" <anthony.tavener@gmail.com>,
"Daniel Bünzli" <daniel.buenzli@erratique.ch>,
"caml list" <caml-list@inria.fr>
Subject: Re: [Caml-list] SDL2 bindings, testers and feedback welcome
Date: Wed, 18 Dec 2013 13:02:09 -0500 [thread overview]
Message-ID: <CAN6ygOm0W759cfXi0_Mun_XF=My8CFnU2r_G2bRg1oQq0wjgQw@mail.gmail.com> (raw)
In-Reply-To: <CAMu2m2+jiWUKFFAu0YVF_dUdtt5YbgshXNZmQkX5c1YPJe+6zw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
What's wrong with thin_sdl? Sounds much nicer than tsdl to me. Or slim_sdl.
-Yotam Barnoy
On Wed, Dec 18, 2013 at 10:40 AM, Ashish Agarwal <agarwal1975@gmail.com>wrote:
> On Tue, Dec 17, 2013 at 2:45 PM, Anthony Tavener <
> anthony.tavener@gmail.com> wrote:
>
> This does raise a question though... should we be concerned about
>> module-name clashes for libraries which should be used "one or the other"?
>>
>
> You never know if someone wants to link in both libraries, so I would say
> yes, you should be concerned.
>
>
> Sdl, Glut, Qt, Gtk, Xml... it's only cryptic at first, and what would you
>> really use which is less cryptic? I can understand the desire to have a
>> library name which at least gives a hint of it's utility, but this isn't
>> possible in the general case without getting some cumbersome names!
>>
>
> Good point. So, I guess I'm saying try hard for a short intuitive name
> first, but yes, sometimes it's not possible.
>
>
[-- Attachment #2: Type: text/html, Size: 2135 bytes --]
next prev parent reply other threads:[~2013-12-18 18:02 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 [this message]
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
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='CAN6ygOm0W759cfXi0_Mun_XF=My8CFnU2r_G2bRg1oQq0wjgQw@mail.gmail.com' \
--to=yotambarnoy@gmail.com \
--cc=agarwal1975@gmail.com \
--cc=anthony.tavener@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;
as well as URLs for NNTP newsgroup(s).