Re: [liblo] Need clarification on method handlers

OK, I can see in server.c at line 1646 that liblo does implicit type coercion.
In my application, integers and floats arguments have different semantic values, is there a way to turn that feature off?

I'd like to discuss if this feature should be kept in liblo 1.0, or make it optional (at the expense of adding a new API for controlling that behavior).  In my experience this only serves a few cases where integers and floats can be freely interchanged, and I honestly did not find a lot of applications where this was the case.


Cam


On 25 mars 2013, at 10:44, Camille Troillard <ca...@os...> wrote:

> Hello,
> 
> Using the latest version on the Github repository.
> If I register the following method handler:
> 
>    lo_server_add_method(server, "/path", "i", MyHandler, user_info);
> 
> And send the message:
> 
>    /path ,f 0.42
> 
> To the server on which the previous handler was registered.  Then I expect that the message is not handled, however liblo calls my handler with the defined "i" type.  I find it surprising, should I?
> 
> 
> Best,
> Cam
>