[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: Kspread row limit
From:       Tomas Mecir <mecirt () gmail ! com>
Date:       2009-12-30 13:39:00
Message-ID: 492258b10912300539y7648d669g3f9adbc87ad4f245 () mail ! gmail ! com
[Download RAW message or body]

2009/12/30 Tomas Mecir <mecirt@gmail.com>:
> These limits add up to a 34-bit number being necessary to store each cell index.

Hm, actually ... it is not uncommon to need more than 32000 rows, but
requiring 32000 columns is very rare, so a quick and easy solution
could be to simply move some of that possible space from columns to
row, something like 2^19 (524,288) rows and 2^12 (4096) columns,
requiring 31 bits to store (signed ints are being used, but if someone
converts them all to unsigned ints, 2^20 rows would be possible
without requiring 64 bits.

The main problem with this is that if someone actually did use more
columns in a previous version of KSpread, they will lose them.

/ Tomas
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]