commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yury Kats (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IO-226) question with byteCountToDisplaySize(long size)
Date Thu, 04 Aug 2011 16:19:27 GMT

    [ https://issues.apache.org/jira/browse/IO-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079442#comment-13079442
] 

Yury Kats commented on IO-226:
------------------------------

What is the reason for rounding down?

.bq. it would have to display the value 2047 as 1.9990234375KB which is not very readable.

This can easily be turned into "1.9" (or "1.99"), which is readable and way more accurate.

Because of the current behaviour, any project I've been on ends up writing its own byteCountToDisplaySize
method and not using FileUtils.
Who needs a method that returns "1 GB" for a 1.99GB file?

> question with byteCountToDisplaySize(long size)
> -----------------------------------------------
>
>                 Key: IO-226
>                 URL: https://issues.apache.org/jira/browse/IO-226
>             Project: Commons IO
>          Issue Type: Improvement
>          Components: Utilities
>            Reporter: shu kai yuan
>             Fix For: 2.0
>
>
> I do not understand the byteCountToDisplaySize(long size) method which is in  class FileUtils
of the package org.apache.commons.io.
> If  the parameter size is 2047 , the method will return 1 KB.Why it will lose precision.
> I read the code. 
> Maybe it is a bug?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message