Changes between Initial Version and Version 1 of Ticket #3865, comment 4


Ignore:
Timestamp:
10/02/17 20:37:40 (5 years ago)
Author:
egmont
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3865, comment 4

    initial v1  
    11Thanks for the bugreport and investigation! 
    22 
    3 I'd prefer the 2nd approach if it indeed works. Especially given the recent (post-4.8.19) "grow file" fixes why not use this feature if we can? In virtual file systems I think it's pretty common and acceptable not to know the file size and report some fake value (e.g. 0 or 4096) in the file listing. 
     3I'd prefer the 2nd approach if it indeed works. Especially given the recent (post-4.8.19) "grow file" fixes why not use this feature if we can? In virtual file systems I think it's pretty common and acceptable not to know the file size in advance and report some fake value (e.g. 0 or 4096) in the file listing. 
    44 
    55Any hardcoded number such as 39 is bound to break in the future, let alone it's not translatable by design (not sure if we're planning to translate these strings but at least with the 2nd approach we could if we wanted to).