After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 323545 - ACCRINT should allow missing "par" argument
ACCRINT should allow missing "par" argument
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Analytics
git master
Other All
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2005-12-08 12:25 UTC by Nick Lamb
Modified: 2010-05-05 06:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Nick Lamb 2005-12-08 12:25:37 UTC 
http://www.ecs.soton.ac.uk/~njl98r/excel/funa.xls

ACCRINT fails with some missing parameters, which is arguably fine, except
for =accrint(33297,33481,33359,0.1,,2) which Excel defines as
equivalent to =accrint(33297,33481,33359,0.1,1000,2)
We'd need a securities expert (or interested amateur) to tell us
if Excel's assumption here is useful, perhaps even expected.
Comment 1 Morten Welinder 2005-12-08 15:50:53 UTC 
Hmm...  It makes perfect sense.  But we actually cannot handle it with our
current argument types.  Observations:

1. Empty is different from missing.  Empty works as zero and yields #NUM.
2. We cannot use '?' as that accepts errors.  (An error at the par argument
   should trump an error at the later arguments.)

We might be able to adapt 'B' as used only by ISNUMBER.  It isn't working
right anyway:
  =AND(ISNUMBER(B1:B3))
in Excel seems to be equivalent to
  =AND(ISNUMBER(B1))

As far as I can see it really, truly, totally ignores stuff in B2:B3: errors,
numbers, blanks, etc..  Regardless of B1's content.
Comment 2 Andreas J. Guelzow 2010-05-05 06:09:22 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.