Passing (un)signed int/longint values to GT.M V5.5 via call-in API

121 views
Skip to first unread message

Tomas Morstein

unread,
Jul 29, 2012, 12:12:23 PM7/29/12
to
Hello,

I am facing a strange call-in problem. I wrote a small self-describing example that reproduces it: https://gist.github.com/3199510

On V5.5x64 the result is:
0: -( 5) is: -5 = -5
1: -( 4) is: -4 = -4
2: -( 3) is: -3 = -3
3: -( 2) is: -2 = -2
4: -( 1) is: -1 = -1
5: -( 0) is: 0 = 0
6: -(-1) is: -1 = 1
7: -(-2) is: -2 = 2
8: -(-3) is: -3 = 3
9: -(-4) is: -4 = 4

...while the expected result (tested on V5.4-002Bx64) is:
0: -( 5) is: -5 = -5
1: -( 4) is: -4 = -4
2: -( 3) is: -3 = -3
3: -( 2) is: -2 = -2
4: -( 1) is: -1 = -1
5: -( 0) is: 0 = 0
6: -(-1) is: 1 = 1
7: -(-2) is: 2 = 2
8: -(-3) is: 3 = 3
9: -(-4) is: 4 = 4

I guess it's a bug of V5.5 itself...

Best regards,
Tom.

K.S. Bhaskar

unread,
Jul 31, 2012, 10:03:10 AM7/31/12
to
Tom --

Thank you for finding and reporting a bug in V5.5-000. The identification number is GTM-7410 and we will fix it in the next release. For what it's worth, GTM-7410 resulted from an imperfect fix in V5.5-000 to an earlier bug (GTM-6994).

Our apologies for the inconvenience and thanks again.

Regards
-- Bhaskar

K.S. Bhaskar

unread,
Sep 20, 2012, 12:53:08 PM9/20/12
to
GTM-7410 is fixed in V6.0-000.

Regards
-- Bhaskar
Reply all
Reply to author
Forward
0 new messages