Re: Is there a 64-bit hex()?

Just because perl issues a warning, it doesn't mean perl doesn't do the right thing. It's true, converting "0x000fffff7f00fffc" with hex is non-portable as it won't do the same thing on a 32-bit perl (to which I say, so what? Adding number isn't portable either, as you may get different results as well, but addition doesn't come with a warning).

$ perl -wE 'say hex "0x000fffff7f00fffc"'
Hexadecimal number > 0xffffffff non-portable at -e line 1.
4503597463175164
[download]

Just use your 64-bit perl, and turn off the warning.

perl -E 'say hex "0x000fffff7f00fffc"'
4503597463175164
[download]

Comment on Re: Is there a 64-bit hex()? Select or Download Code

Replies are listed 'Best First'.
Re^2: Is there a 64-bit hex()? by ikegami (Patriarch) on Feb 10, 2009 at 14:44 UTC
Better yet: `no warnings 'portable'; # Support for 64-bit ints required` [download]	[reply] [d/l]
Re^2: Is there a 64-bit hex()? by Minok (Novice) on Feb 10, 2009 at 19:52 UTC
I just want to clarify my understanding here. So perl is providing the decimal equivalent of the 64 bit hex string given to it by saying that this hex string is equivalent to the following decimal number: 4,503,597,463,175,164. The remaining question is about portability, or more specifically, will you get the same value regardless on which machine you run this perl code (ie would some other run produce a different decimal representation (assuming all would agree to interpret a 64 bit hex number as a 64-bit unsigned integer representation without any Endian manipulation needed, that is just straight binary from MSbit to LSbit from left to right) )? And/Or would one even get an answer on some other machine (would some Perl interpreter, running on some hardware, not provide any result) ?	[reply]
Re^3: Is there a 64-bit hex()? by JavaFan (Canon) on Feb 10, 2009 at 21:29 UTC
If you get a different result on a different platform, assuming both perls are compiled with 64-bit integers you have discovered a currently unknown bug. But you are likely to get a different result if you do the same with 32-bit integer perl. The portability issue the warning warns about is the portability between 32-bit and 64-bit perls. (perls, not hardware).	[reply]