Re: Strange behavior when printing a 4G+ integer on 32bits platform.

2018-11-13 Thread sisyphus
On 11/13/2018 8:07 AM, Tetsuo Handa wrote: > Hello. > > I want to represent up to a few hundreds gigabytes for file size. > > On 32bits platform, I noticed that > >my $value = ...; >printf("%u\n", $value); > > prints 4294967295 if $value >= 4294967295 whereas > >my $value = ...; >pr

Re: Common regex for timedate

2018-11-13 Thread Asad
Hi Andy , thanks for the reply . Yes the purpose is to compare the timestamps ans yes these are the only two formats . Thanks, On Wed, Nov 14, 2018 at 2:48 AM Andy Bach wrote: > Calling upgrade.sql on 05-JUL-18 10.19.42.559000 PM -12 > Calling apply.sql on 17.10.18 12:28:12,447849

Re: Common regex for timedate

2018-11-13 Thread Andy Bach
Calling upgrade.sql on 05-JUL-18 10.19.42.559000 PM -12 Calling apply.sql on 17.10.18 12:28:12,447849 +02: > I created on regex : \d\d\.\d\d\.\d\d\s[012][0-9]:[0-5][0-9]>:[0-5][0-9] > this only matches : Calling apply.sql on 17.10.18 12:28:12,447849 +02: Right as your first string has word chars

Re: Strange behavior when printing a 4G+ integer on 32bits platform.

2018-11-13 Thread Mike Flannigan
I don't have an answer for you, but I find this interesting.  I note the same issue in 64bit up near 18446744073709551615 I'm guessing the guy who wrote Math::BigInt may have the answer. Mike On 11/13/2018 8:07 AM, Tetsuo Handa wrote: Hello. I want to represent up to a few hundreds gigaby

Strange behavior when printing a 4G+ integer on 32bits platform.

2018-11-13 Thread Tetsuo Handa
Hello. I want to represent up to a few hundreds gigabytes for file size. On 32bits platform, I noticed that my $value = ...; printf("%u\n", $value); prints 4294967295 if $value >= 4294967295 whereas my $value = ...; printf("%s\n", $value); and use Math::BigInt; my $value = ...;

Re: Common regex for timedate

2018-11-13 Thread Дмитрий Ананьевский
On Mon, 12 Nov 2018 18:18:12 +0530 Asad wrote: > Hi all , > >I have two stings from logfile how can we have a common regex so > that its parse datetime details for further parsing ; > > Calling upgrade.sql on 05-JUL-18 10.19.42.559000 PM -12 > Calling apply.sql on 17.10.18 12:28:12,