Message93509
Thanks for the explanation, and I agree that decimal.py is perfectly
correct. I based the report on the fact that decNumber updates the
context status with e.g. Division_impossible. But Division_impossible is
one of the flags that form IEEE_754_Invalid_operation, so presumably the
intention is to signal IEEE_754_Invalid_operation by means of flagging
Division_impossible.
On a side note, I find the distinction between signals and exceptional
conditions (mandated by the spec, as you pointed out) needlessly
complicated and I'm happy to see that note 5 under "Abstract
representation of context" says this might change in the future.
I'm all for raising DivisionImpossible, if it is not too much trouble. |
|
Date |
User |
Action |
Args |
2009-10-03 22:06:49 | skrah | set | recipients:
+ skrah, mark.dickinson |
2009-10-03 22:06:48 | skrah | set | messageid: <1254607608.88.0.541939145191.issue7046@psf.upfronthosting.co.za> |
2009-10-03 22:06:47 | skrah | link | issue7046 messages |
2009-10-03 22:06:46 | skrah | create | |
|