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 90A567EE99 for ; Sun, 22 Dec 2013 11:01:46 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of kakadu.hafanana@gmail.com) identity=pra; client-ip=209.85.220.42; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="kakadu.hafanana@gmail.com"; x-sender="kakadu.hafanana@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of kakadu.hafanana@gmail.com designates 209.85.220.42 as permitted sender) identity=mailfrom; client-ip=209.85.220.42; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="kakadu.hafanana@gmail.com"; x-sender="kakadu.hafanana@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-pa0-f42.google.com) identity=helo; client-ip=209.85.220.42; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="kakadu.hafanana@gmail.com"; x-sender="postmaster@mail-pa0-f42.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnEKAGG3tlLRVdwqlGdsb2JhbABYg0NVpkiSPDcCAoEKCBYOAQEBAQcLCwkSKoIlAQEBBEABGxIMAwwGBQsNDSEhAQERAQUBChIZEoddAQMRDaUBjFyDCY5eChknAwpkhW4RAQUMjQYZgSJfFoQgBIk9hX6GcIFsgTCLKoNNGCmEXjeBLA X-IPAS-Result: AnEKAGG3tlLRVdwqlGdsb2JhbABYg0NVpkiSPDcCAoEKCBYOAQEBAQcLCwkSKoIlAQEBBEABGxIMAwwGBQsNDSEhAQERAQUBChIZEoddAQMRDaUBjFyDCY5eChknAwpkhW4RAQUMjQYZgSJfFoQgBIk9hX6GcIFsgTCLKoNNGCmEXjeBLA X-IronPort-AV: E=Sophos;i="4.95,530,1384297200"; d="scan'208";a="42012471" Received: from mail-pa0-f42.google.com ([209.85.220.42]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 22 Dec 2013 11:01:45 +0100 Received: by mail-pa0-f42.google.com with SMTP id lj1so4338112pab.15 for ; Sun, 22 Dec 2013 02:01:43 -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 :content-type; bh=xjgbDmSYbmM7Cd7vk1bcMzPQD13atz2uN1EqTLXljrE=; b=D52Rk/l9JLZ1X5cyYd78zbPPMUK/Z2s/ERgxd2wnXzm9Td46gkTnrWW2G8m+qFCuUg YGdYXmAOTlwIEAbiETaIM6mUaMrny4fHii9cIo6Y066KP658OvfMEm0WLj1o0ECEdfAz b8JQAHZvOogHsqJqldcDfB/cYxbhxXo0SeJgX95pdbRJr2qGI5dEXZt36L2fkL0wgkbZ kRlRB+2tGOTsM+FmpWQfpehAKm2KuNEk3HmPCuhfvbj/iz6FuGXNKcGr+CNTdxNbIs9p cisMIaLD86mbG6ALzMBBXdCcZ7BkBm9Ssu7ZqEDwTzdxCM8Fdt6zL8+w1k4aouFTn1cv +V8A== MIME-Version: 1.0 X-Received: by 10.67.3.34 with SMTP id bt2mr19118844pad.3.1387706503640; Sun, 22 Dec 2013 02:01:43 -0800 (PST) Received: by 10.70.19.37 with HTTP; Sun, 22 Dec 2013 02:01:43 -0800 (PST) In-Reply-To: References: <4DDEBB7487B641C0834F09D522EA9918@erratique.ch> Date: Sun, 22 Dec 2013 14:01:43 +0400 Message-ID: From: Kakadu To: caml-list@yquem.inria.fr Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Caml-list] SDL2 bindings, testers and feedback welcome Fellas, I have added [1] function TTF_openFont but when I use it I receive `Error and don't know why. Do you know how to debug it? Maybe I did something wrong in OCaml definitions? Kakadu [1] https://github.com/Kakadu/tsdl/commit/44115cbdee92911eae9b1d51ce33da86392da965#diff-844c2aaff3869f0a29cc34c69b019276R824 On Wed, Dec 18, 2013 at 12:18 PM, Florent Monnier wrote: > 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 > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs