Page 2 of 2

Re: x2d() bug

Posted: Mon Oct 18, 2021 9:06 pm
by nbache
The signed/unsigned thing was in relation to the TRL-2 definition, i.e. Rexx, not necessarily ARexx.

I don't know enough about it to judge whether there is indeed a bug here, but I suspect it's more of a limitation rooted in the age of our implementation (32/64 bit etc.).

But if someone knows more, I'm eager to hear it.


Best regards,

Niels

Re: x2d() bug

Posted: Wed Oct 20, 2021 6:14 pm
by polluks
Look at my first statement, there's a signed/unsigned thing, without Rexx knowledge you won't understand it.

Re: x2d() bug

Posted: Wed Oct 20, 2021 6:30 pm
by nbache
I do have quite a bit of (A)Rexx knowledge, and I do understand what you're explaining in the first post.

What I'm not sure about is whether this issue is simply to be expected from our implementation with its limitations.

Best regards,

Niels