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 A403E7EC6E for ; Wed, 18 Dec 2013 09:18:09 +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=74.125.82.178; 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 74.125.82.178 as permitted sender) identity=mailfrom; client-ip=74.125.82.178; 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-we0-f178.google.com) identity=helo; client-ip=74.125.82.178; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="monnier.florent@gmail.com"; x-sender="postmaster@mail-we0-f178.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArgDAM1ZsVJKfVKylGdsb2JhbABZg0JVuGaBCwgWDgEBAQEHCxQSKoIlAQEBAwFAARsdAQMBCwYFCwMKLiIBEQEFARwGG4dnAQMJCA2kVoxagwmNRQoZJw1khhgRAQUMji5YB4Q2BJgWkCcYKYRYO4Es X-IPAS-Result: ArgDAM1ZsVJKfVKylGdsb2JhbABZg0JVuGaBCwgWDgEBAQEHCxQSKoIlAQEBAwFAARsdAQMBCwYFCwMKLiIBEQEFARwGG4dnAQMJCA2kVoxagwmNRQoZJw1khhgRAQUMji5YB4Q2BJgWkCcYKYRYO4Es X-IronPort-AV: E=Sophos;i="4.95,506,1384297200"; d="scan'208";a="41530389" Received: from mail-we0-f178.google.com ([74.125.82.178]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 18 Dec 2013 09:18:09 +0100 Received: by mail-we0-f178.google.com with SMTP id u57so7003471wes.23 for ; Wed, 18 Dec 2013 00:18:08 -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=P43HrNpftOJx7QuOTf3rZJcLzNpFTrnjvNAzuIPcoQY=; b=kp+BjrnssgVI1Z8oDAenaRvwUa/T1udLeWg6+g9qfxVhhiGmVGij8oEfSgDarjqqyB ReWplQm2/F9VY5AeG6nC7xZrvHyDvDdr4SFsGAb3U7sSGVrU6fNABTkcMGUeLbsbhcBG yBujMFO7w+/lS1DUeL/oumuuy1pj1PQZm72t/Ke6n7plN4gC1xsDTEzAE+NiY39Om6zy 5VHWQUdk7FZXqciicKt+LNPdwoxG4BrvcNTRoGzGP3T7+2em9MwyHNmzyJtmU4Mr/eDX Wy8hqg+VB5TR1+DK9YUa2Xk+qNZCXgdi2cotVICQr5NQMsLQVFzUWe+saAZFWaK1607k hiFQ== MIME-Version: 1.0 X-Received: by 10.194.77.140 with SMTP id s12mr810818wjw.86.1387354688720; Wed, 18 Dec 2013 00:18:08 -0800 (PST) Received: by 10.194.77.110 with HTTP; Wed, 18 Dec 2013 00:18:08 -0800 (PST) In-Reply-To: References: <4DDEBB7487B641C0834F09D522EA9918@erratique.ch> Date: Wed, 18 Dec 2013 09:18:08 +0100 Message-ID: From: Florent Monnier To: Erkki Seppala Cc: caml-list@yquem.inria.fr Content-Type: text/plain; charset=ISO-8859-1 X-Validation-by: monnier.florent@gmail.com Subject: Re: [Caml-list] SDL2 bindings, testers and feedback welcome 2013/12/18, Erkki Seppala wrote: > Florent Monnier wrote not only: > >> More precisely I found very interesting several initiatives available >> around, like for example the idea behind the XML description of the >> API of the XCB C library. >> >> http://xcb.freedesktop.org/dist/xcb-proto-1.9.tar.gz > > I suppose it doesn't detract your point, but xcb-proto actually > describes the line protocol of X, not the X library interface or XCB > library interface though the latter can be inferred from it based on the > fact it's generated. So the new XCB-based libraries for interacting with > the X server then are generated from those (but Xlib is not related to > this). They are not very useful for binding per se. > > But they could be used for generating XCB-based OCaml library > interacting directly with X. (I have actually written a tool based on > those that decodes live X traffic, but it was in Python (for code > generation) and C (for doing the work).) What I meant is that annotate the C headers, or similar approaches are limited if it's about to make a generic way that could be used in most (or maybe almost all) cases. A proper description of the APIs would make it possible to divert to different languages (and maybe even other kind of applications). XcbProto is designed for our best friend Python, but its upstream immediatly proposed to complete it with additional elements that we would need for our programming language of choice. > Well, I think that it may be a bit unrealistic to expect this kind of > fork to get very popular. I think in most common SDL use cases people > just don't care much about errors :(. (Ie. games: either work or they > don't.) Sorry it was just ironic :) Sam already does quite a lot enough. We should not ask too much, or if we do we should just do ourself what we request from someone else. > But a documentation effort or a tool for extracting thrown error strings > and then building towards more consistent error management, that I think > would easily be upstreamable. Then please try! -- Best regards Florent