Saying its a pain might be over stating it a bit, however it does need its inter-language interfacing beefing up, a great deal of external libraries not to mention os api's use c structs and dealing with them can be a nightmare
being able to use C objects would be a dream I've lost count of the numbe of times I've had to do loads of tiny seperate get and set functions like this (real tedious work!)
I've found the debugger to be fairly poor when dealing with external libs, often showing the error line a random distance from the actual function call that caused the problem, some kind of itergration with gdb would be nice as an alternitive.
Mark seem to have a pathalogical lothing of including C structs in Max (or at least thats the impression I get) which is a real shame...
Which is a real shame, not only for us, but for brl sales.
being able to use C objects would be a dream I've lost count of the numbe of times I've had to do loads of tiny seperate get and set functions like this (real tedious work!)
extern "C" int GetSomeParam(aCobject* e, int op, int index) { return e->GetSomeParam(op, index); }
I've found the debugger to be fairly poor when dealing with external libs, often showing the error line a random distance from the actual function call that caused the problem, some kind of itergration with gdb would be nice as an alternitive.
Mark seem to have a pathalogical lothing of including C structs in Max (or at least thats the impression I get) which is a real shame...
Which is a real shame, not only for us, but for brl sales.