|Think about Loose Coupling|
Re: Another 64-bit Perl bug. Is it fixed post 5.18?by thanos1983 (Parson)
|on May 24, 2015 at 13:56 UTC||Need Help??|
I running on: This is perl 5, version 18, subversion 2 (v5.18.2) built for x86_64-linux-gnu-thread-multi and I can see two different observations based on your script.
When I am executing your script with new line characters \n sample of the script bellow:
I am getting the following output:
But when I remove the new line characters \n sample of code bellow:
I get on the output:
So based on the observations/results provided by karlgoethebier above, shows that if you have appropriate HW, you can get a complete output on v5.18.2 even if with the new line characters. Instead of my HW failure. Although that on the 4th print statement he is getting a zero indicating that probably Perl v5.18.2 can not handle so big numbers.
So in conclusion I would say a combination of HW and latest SW version of Perl can provide you with the result that you expect.
Update: I am not expert (not even close) but I think this might be the reason. Short description about memory limitation between LinuxOS and WindowsOS Memory Limits in R.
Update 2: I also found this regarding Perl 5.20.0 Better 64-bit support:
On 64-bit platforms, the internal array functions now use 64-bit offsets, allowing Perl arrays to hold more than 2**31 elements, if you have the memory available. The regular expression engine now supports strings longer than 2**31 characters. perl #112790, #116907 The functions PerlIO_get_bufsiz, PerlIO_get_cnt, PerlIO_set_cnt and PerlIO_set_ptrcnt now have SSize_t, rather than int, return values and parameters..
Update 3: update hyper-link and modified text output.
Hope this helps.
Seeking for Perl wisdom...on the process of learning...not there...yet!