jasch

I'm the process of recompiling for FAT externals, and I come across this broken functionality:

It's basically traversing a linked list of instances of another class using the mess4 macro from ext_mess.h to remotely call the paint methods from these clients.

Operand of type 'double' cannot be cast to a pointer type

Operand of type 't_pt' (aka 'struct _pt') where arithmetic or pointer type is required

t_pt origin;
double size;
void  *client;

client = linklist_getindex(x->registered_controllers, 0);
while(client)
{
    mess4((t_object *)client, ps_paint, g, origin, size, 1);
    linklist_next(x->registered_controllers, client, (void *)&client);
}

P.S. this could also be due to an update of Xcode to 12.4, which might react more strictly to types?

It's basically traversing a linked list of instances of another class using the mess4 macro from ext_mess.h to remotely call the paint methods from these  clients.

both errors are on the mess4 line:
Operand of type 'double' cannot be cast to a pointer type
Operand of type 't_pt' (aka 'struct _pt') where arithmetic or pointer type is required

t_pt origin;
double size;
void  *client;

client = linklist_getindex(x->registered_controllers, 0);
while(client)
{
	mess4((t_object *)client, ps_paint, g, origin, size, 1);
	linklist_next(x->registered_controllers, client, (void *)&client);
}

Hi, 
I'm the process of recompiling for FAT externals, and I come across this broken functionality:
It's basically traversing a linked list 

trouble-with-mess4-macro-from-ext-mess-for-8-2-api

hi Jasch, thanks much for diving into updating your externals!

I can make some suggestions, but it's tricky to diagnose this without the source. There are significant changes wrt to calling object methods due to apple silicon compatibility needs. Passing double arguments to untyped method calls is no longer supported. I believe the solution is to use 

, which requires passing in both the return type and signature of the calling method. You can check the header for the full documentation of this call.

for your example it would look something like this (assuming a return type of 

object_method_direct(t_max_err, (t_object *, t_jgraphics*, t_pt, double, long),(t_object *)client, ps_paint, g, origin, size, 1);

Please let me know if that doesn't get you going.

I can make some suggestions, but it's tricky to diagnose this without the source. There are significant changes wrt to calling object methods due to apple silicon compatibility needs. Passing double arguments to untyped method calls is no longer supported. I believe the solution is to use object_method_direct, which requires passing in both the return type and signature of the calling method. You can check the header for the full documentation of this call.

for your example it would look something like this (assuming a return type of t_max_err, and argument g is a t_jgraphics):

object_method_direct(t_max_err, (t_object *, t_jgraphics*, t_pt, double, long),(t_object *)client, ps_paint, g, origin, size, 1);
Please let me know if that doesn't get you going.

Adapting the remote method calls from the mess4 macro to the object_method_direct seems to have done the trick. tbc.

Adapting the remote method calls from the mess4 macro to the object_method_direct seems to have done the trick. tbc.

cheers

trouble with mess4 macro from ext.mess for 8.2 API