Hi Leonard, On Thursday, 2008-08-07 21:17:34 +0300, Leonard Mada wrote:
>> The reason why interpreting strings as numeric values on the fly is >> harmful and we do not want to implement it. > > BUT you do it. You interpret it *always* as 0. This is the worst > possible scenario. It is at least consistent for =A1+A2 and =SUM(A1:A2). > As I mentioned in the previous post: raising an error is one option (the > best), but it depends on some pre-requisites: > - ability to easily find string-as-number cells > - easy conversion to number > [I know that Cor's extension does exist, > BUT Calc should do it natively] No. Why should it? If an extension can do all work there is no need to reimplement it in the core again. Eike -- OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer. SunSign 0x87F8D412 : 2F58 5236 DB02 F335 8304 7D6C 65C9 F9B5 87F8 D412 OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't send personal mail to the [EMAIL PROTECTED] account, which I use for mailing lists only and don't read from outside Sun. Use [EMAIL PROTECTED] Thanks.
pgpPjYuT5MAZQ.pgp
Description: PGP signature
