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 9C6E87EC6E for ; Tue, 17 Dec 2013 20:45:54 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of anthony.tavener@gmail.com) identity=pra; client-ip=209.85.215.182; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="anthony.tavener@gmail.com"; x-sender="anthony.tavener@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of anthony.tavener@gmail.com designates 209.85.215.182 as permitted sender) identity=mailfrom; client-ip=209.85.215.182; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="anthony.tavener@gmail.com"; x-sender="anthony.tavener@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-ea0-f182.google.com) identity=helo; client-ip=209.85.215.182; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="anthony.tavener@gmail.com"; x-sender="postmaster@mail-ea0-f182.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AocBAB6psFLRVde2nGdsb2JhbABZhAsMuGmBGAgWDgEBAQEBBg0JCRQogiUBAQEDAUABGx0BAwELBgULDS4hAQERAQUBHAYTh28BAwkIpQyMWoMJjSYKGScNZIYYEQEFDIxzghMHhDYEiUOMaIFrjFqDTRgphHcc X-IPAS-Result: AocBAB6psFLRVde2nGdsb2JhbABZhAsMuGmBGAgWDgEBAQEBBg0JCRQogiUBAQEDAUABGx0BAwELBgULDS4hAQERAQUBHAYTh28BAwkIpQyMWoMJjSYKGScNZIYYEQEFDIxzghMHhDYEiUOMaIFrjFqDTRgphHcc X-IronPort-AV: E=Sophos;i="4.95,502,1384297200"; d="scan'208";a="41478928" Received: from mail-ea0-f182.google.com ([209.85.215.182]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 17 Dec 2013 20:45:53 +0100 Received: by mail-ea0-f182.google.com with SMTP id a15so3103446eae.41 for ; Tue, 17 Dec 2013 11:45:53 -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; bh=Hh27/nyY56PM1lBvDfb1a0nolHIUOAHDdukHexiKTSc=; b=IXmMZiQ08rTJ6xNWw5E4agRAccX/YYA1KuC6F9AF4sSudZhPt9YH/X+AoouDI7JUBW 1O/uNBzWnSPIX1L8zw1XDsEiTcRfOv1R4sSl809bKQ+JnoDW/j9HBRrtdxkDr24chIZj CnpMahu2FjNgaBs3KmGjRzY4frJoei8TSfRvhDIsqJAR8zp8Ze0LC/HJhD+YLFvQ/5tz x+uQ7PhKg3XEBjVMWo0BNfkUbt4SyA3GH9Lt9Sr7UCzeCBat2nz4gKKVnICTUasCPsIf 7Ea0TPFGOkCxQUjjLngQFhLLz27HOnsXgvGwbyDOrG6LFfHhuPFLSvwPoaPJytNtrHe8 Heog== MIME-Version: 1.0 X-Received: by 10.14.251.132 with SMTP id b4mr25148197ees.78.1387309552366; Tue, 17 Dec 2013 11:45:52 -0800 (PST) Received: by 10.15.90.202 with HTTP; Tue, 17 Dec 2013 11:45:52 -0800 (PST) In-Reply-To: References: <4DDEBB7487B641C0834F09D522EA9918@erratique.ch> <1C9496037B6149EC970D65C3BFA490F7@erratique.ch> Date: Tue, 17 Dec 2013 12:45:52 -0700 Message-ID: From: Anthony Tavener To: Ashish Agarwal Cc: =?ISO-8859-1?Q?Daniel_B=FCnzli?= , caml list Content-Type: multipart/alternative; boundary=001a1133d59c0ffb3a04edc02d80 Subject: Re: [Caml-list] SDL2 bindings, testers and feedback welcome --001a1133d59c0ffb3a04edc02d80 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On Tue, Dec 17, 2013 at 11:57 AM, Ashish Agarwal wro= te: > On Tue, Dec 17, 2013 at 12:47 PM, Daniel B=FCnzli < > daniel.buenzli@erratique.ch> 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 are multiple sdl and opengl bindings. I think there was another ocamlsdl aside from the current OCamlSDL, and there's sdlcaml which is packed with glcaml. For OpenGL, there's LablGL, glMLite, and glcaml. And these are the package names, rather than the module names. It's ripe territory for naming clashes. :) I've taken an initial stab at my own SDL2 bindings and I've been using Sdl2 as the module name (sdlcaml uses Sdl as it's module name), but expected that I might change that to something more distinct if I were to share it. This does raise a question though... should we be concerned about module-name clashes for libraries which should be used "one or the other"? I don't know if some build tool might find libraries by module name now or in future -- if so, unique module names are important. If not, then I guess using the same module name is fine, but with a distinct package name. >> > I don't like random single letters in names, which is also a problem in >> your Vg and Gg project names. >> >> It's not random ! It's short cryptic acronyms. Vector graphics, geometry >> and graphics=85 >> > > 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. > > 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! --001a1133d59c0ffb3a04edc02d80 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable

= On Tue, Dec 17, 2013 at 11:57 AM, Ashish Agarwal <agarwal1975@gmail.co= m> wrote:
=
On Tue, Dec 17, 2013 at 12:47 = PM, Daniel B=FCnzli <daniel.buenzli@erratique.ch> = wrote:
I could have used Sdl but I don't like to take ownership of toplevel n= ames that are used in other settings.

=
Admirable, but if you're defining a library that binds to a C libr= ary, I think it is reasonable to take that name. We rarely have multiple OC= aml libraries that bind to the same C library. In this case, the library na= me could be sdl or ocaml-sdl (or sdl2 or ocaml-sdl2). I usually don't l= ike adding "ocaml-" to library names because it is silly; of cour= se it is an ocaml library. However, when binding to a C library, it makes s= ome sense to distinguish between the OCaml and original C libraries.


There are multiple sdl and opengl bindings. I think there was another oc= amlsdl aside from the current OCamlSDL, and there's sdlcaml which is pa= cked with glcaml. For OpenGL, there's LablGL, glMLite, and glcaml. And = these are the package names, rather than the module names. It's ripe te= rritory for naming clashes. :) I've taken an initial stab at my own SDL= 2 bindings and I've been using Sdl2 as the module name (sdlcaml uses Sd= l as it's module name), but expected that I might change that to someth= ing more distinct if I were to share it.

This does raise a question though... should= we be concerned about module-name clashes for libraries which should be us= ed "one or the other"? I don't know if some build tool might = find libraries by module name now or in future -- if so, unique module name= s are important. If not, then I guess using the same module name is fine, b= ut with a distinct package name.


> I don't like random single letters in names, which is also a probl= em in your Vg and Gg project names.

It's not random ! It's short cryptic acronyms. Vector graphic= s, geometry and graphics=85

I mis= spoke. What I meant is: I don't like short cryptic acronyms. They appea= r random to me because I don't know what they mean.


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 possibl= e in the general case without getting some cumbersome names!

--001a1133d59c0ffb3a04edc02d80--