Not able to compile ZeroMQ. Calls from Red(not System): handle! != byte-ptr! about code HOT 6 CLOSED

Change of a single line is not enough, as there are other usages of handle! in the source code, nor does it solve the actual problem.

Red/System rightfully warns you and rejects such macro redefinition (that's the reason of compilation error - there's a type mismatch in library call, because old definition is still being used), as it's a ticking bomb that may cause serious trouble, e.g. Red runtime relies on handle! pretty heavily, esp. in OS APIs.

Anyway, this code is not maintained for a long time and serves only as a PoC, you shouldn't use it as-is for your project. Red itself will likely have ZeroMQ port in the future.

from code.

Yes, i understood that it's not nice fix.
And i'm ok with that not maintained - i too just playing with red (try to implement IPython kernel with red).
It's ok, to change handle! definition to something another name or remove it?

from code.

@Oldes ☝️

from code.

@Intey what if you just remove this line?

Apparently there was no handle! used in Red's runtime when I was working with it.

from code.

As in the source is handle! used mostly instead of void *, it should be ok.

from code.

@Oldes I think about this. But I meet nice idea of name types explicit. Something like context-ptr! like with socket-ptr!. I prepare PR to show this

_{Sent with GitHawk}

from code.