On 21 Feb 2010, at 01:22, Andrew Thompson wrote:

Aye, there's the rub. You see all we know about the param type (at the moment)
is that it is Java boolean.

This was the gist of my example passing it as Object - the mapping at the moment
is entirely JNA, and JNA assumes that the Java type maps to the correct native
type.

Now it seems to me that we have 3 options.

1 - Pick a mapping and stick to it. So Java boolean (actually Boolean by the
time we get to the invocation) always maps to int32 with 1 = YES, 0 = NO.

2 - Look up the method signature for the selector that we are about to invoke,
and use that to inform our mapping. This is slow, but could be cached, and would
allow us to finesse our current silly issues with having to use CGFloat etc as
classes.

3 - Map boolean -> BOOL and provide an annotation to specify exceptions.

I'm actually quite keen on 2, but one is obviously simplest. Does anyone have an
example of a Mac API where JNA's default mapping actually makes sense, because
if not maybe we should suggest the change there?

Duncan