in reply to How do I get correct file size for huge file under Win32?

If you used print it will be displayed correctly:

C:\test>dir huge.3.5GB 2008-11-25 09:29 3,758,096,387 huge.3.5GB 1 File(s) 3,758,096,387 bytes C:\test>perl -wle"print -s $ARGV[ 0 ]" huge.3.5GB 3758096387

You'll only see the problem if you use printf with %d:

C:\test>perl -wle"printf qq[%d\n], -s $ARGV[ 0 ]" huge.3.5GB -536870909

And you can avoid that by using %f or %u instead:

C:\test>perl -wle"printf qq[%.f\n], -s $ARGV[ 0 ]" huge.3.5GB 3758096387 C:\test>perl -wle"printf qq[%u\n], -s $ARGV[ 0 ]" huge.3.5GB 3758096387

However, %u is limited to 2**32-1 (a limitation by design that %.f doesn't have):

C:\test>dir huge.6.0GB 2008-11-25 09:40 6,442,450,947 huge.6.0GB 1 File(s) 6,442,450,947 bytes C:\test>perl -wle"printf qq[%u\n], -s $ARGV[ 0 ]" huge.6.0GB 4294967295 C:\test>perl -wle"printf qq[%.f\n], -s $ARGV[ 0 ]" huge.6.0GB 6442450947

This "problem" is nothing to do with filesizes (or win32 per se), but rather that printf %d treats numbers as signed integers, so values between 2**31 and 2**32 are displayed as negative. They are held correctly internally.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Replies are listed 'Best First'.
Re^2: How do I get correct file size for huge file under Win32?
by SadEmperor (Novice) on Nov 25, 2008 at 11:51 UTC
    but I didn't use printf yet...
    I use print in your way.