From: Kakadu <kakadu.hafanana@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] SDL2 bindings, testers and feedback welcome
Date: Sun, 22 Dec 2013 14:01:43 +0400 [thread overview]
Message-ID: <CAGmVoG2btBFkQ_aCo2=YJF_-VjdGPnf-AL_B7P5go08Ns4F+2w@mail.gmail.com> (raw)
In-Reply-To: <CAE1DttBJsSwHdo3R6rAFZjoSpUWCuop5HDFxTqN7UJ4Gq92GEw@mail.gmail.com>
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
<monnier.florent@gmail.com> 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
next prev parent reply other threads:[~2013-12-22 10:01 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 [this message]
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
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='CAGmVoG2btBFkQ_aCo2=YJF_-VjdGPnf-AL_B7P5go08Ns4F+2w@mail.gmail.com' \
--to=kakadu.hafanana@gmail.com \
--cc=caml-list@yquem.inria.fr \
/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