CoCoA » CoCoALib

02 Jul 2024

21:45 Feature #92: Error Codes: BadIndex

*@BadIndex@* is fine; while *@IndexOutOfRange@* is slightly more descriptive, it is harder to read and not really any... John Abbott

10:38 Feature #92: Error Codes: BadIndex

Now I'm less inclined to rename "BadIndex".
However, I've just noticed that we have some relatives: e.g. "BadIndetIn... Anna Maria Bigatti

17:08 Design #427: Error names and error messages (current design)

Changed Not... into
ReqNonNegative, ReqNonNegativeGrading, ReqPositive, ReqPositiveGrading
and quite a few
@CoCo... Anna Maria Bigatti

17:07 Design #308: Error: ERR::NotNonZero instead of ERR::ZeroRingElem? [--> ReqNonZero]

> > JAA thinks that @LogZero@ should be merged with @NotNonZero@.
done Anna Maria Bigatti

11:33 Design #308: Error: ERR::NotNonZero instead of ERR::ZeroRingElem? [--> ReqNonZero]

John Abbott wrote:
> All CoCoALib errors which refer to zero are:
> *@BadPwrZero, DivByZero, LogZero, MemPoolZero, ... Anna Maria Bigatti

11:01 Design #308: Error: ERR::NotNonZero instead of ERR::ZeroRingElem? [--> ReqNonZero]

The current decision is for *ReqNonZero*.
Moreover, similarly as *BadIndex*, I suggest grouping the similar errors a... Anna Maria Bigatti