As discussed in IRC, nevermind this. I misread the header files.
On 4 August 2014 01:12, Auke Booij wrote:
> On 30 July 2014 20:27, Pekka Paalanen wrote:
>> Actually no. Binding writers are expected to write their own code
>> generator for their language, like wayland-scanner is for C. You
>> ar
On 30 July 2014 20:27, Pekka Paalanen wrote:
> Actually no. Binding writers are expected to write their own code
> generator for their language, like wayland-scanner is for C. You
> are expected to not use the static inline generated C functions.
>
> All the static inline functions are not part of
On Sun, 3 Aug 2014 17:07:44 +0200
Auke Booij wrote:
> >> Speaking of which, is there a reason the code samples don't show up
> >> correctly in the online documentation?
> >
> > Which code samples exactly?
>
> http://wayland.freedesktop.org/docs/html/chap-Library.html
> - wl_list
> - wl_display_p
On 3 August 2014 09:08, Pekka Paalanen wrote:
> It was, hidden in a small paragraph in the documentation...
I have to apologize, you are right.
>> I guess that this is convention in C?
>
> [...]
Thanks for your perfectly clear explanation, that does clarify it a lot.
>> Speaking of which, is t
On Sat, 2 Aug 2014 15:07:19 +0200
Auke Booij wrote:
> On 30 July 2014 20:27, Pekka Paalanen wrote:
> > Actually no. Binding writers are expected to write their own code
> > generator for their language, like wayland-scanner is for C. You
> > are expected to not use the static inline generated C
On 30 July 2014 20:27, Pekka Paalanen wrote:
> Actually no. Binding writers are expected to write their own code
> generator for their language, like wayland-scanner is for C. You
> are expected to not use the static inline generated C functions.
Okay, that makes some amount of sense. But in that
On Wed, 30 Jul 2014 15:00:55 +0200
Auke Booij wrote:
> I am in the process of writing bindings to Wayland for Haskell, and
> have run into some issues which I think you may be interested in
> solving.
...
> 2. The current wayland-scanner produces a huge amount of "static
> inline" functions. In
I am in the process of writing bindings to Wayland for Haskell, and
have run into some issues which I think you may be interested in
solving.
They all relate to the protocol files.
1. Haskell is a very richly typed language, which means that if two
integers have different meaning (e.g. length of
