in reply to Re: Lost in unpack hell
in thread Lost in unpack hell

</cite>The long string you gave for ClOrdID translates to 04C6A29EBAD1E5BB(base16). You're expecting 4295075805(10) = 000000010001A7DD(16) No matter how you rearrange the hex digit pairs, those will never match. It's clearly not a byte ordering problem. </cite> Then that means that the other program is "lying" to me, which _is_ possible I guess since it appears to have other problems. I tried the unpack string you mentioned :
>> unpack 'a a n N Q> a*'
but I get : Invalid type 'Q' in unpack at /opt/devel/mdscripts/PerfAgent/lib/enxtUtpDirect.pm This is (I believe)because I'm not using a 64bit perl and I can't because of some PERL packages I am using. Given this, can I use something other than 'Q' ?? Thanks very much for the assistance, it is much appreciated

Replies are listed 'Best First'.
Re^3: Lost in unpack hell
by zentara (Cardinal) on Feb 11, 2010 at 12:19 UTC
      thanks very much !!
Re^3: Lost in unpack hell
by ikegami (Patriarch) on Feb 11, 2010 at 16:00 UTC

    Then that means that the other program is "lying"

    No, that does not necessarilly follow from what I said.

      Well maybe not but since I currently lack the knowledge to reliably decode what's the in message it's difficult to draw another conclusion. I'll keep trying but I now seem to have come up against the issue of trying to decode a quad effectively(though I will try the suggestion from Zentara) Thanks for your help by the way !!