Activity
From 01 Jul 2024 to 30 Jul 2024
Today
-
17:54 Design #427: Error names and error messages (current design)
- Anna Maria Bigatti wrote:
> "BLAH must be at least 2 and fit into a long" or "BLAH must be at least 2".
> I think w... -
17:14 Design #427: Error names and error messages (current design)
- I've changed some more Not into Req.
I removed @ModulusLT2@ because unused.
There is @BadModulus@ ("Modulus must ... -
11:17 Feature #92: Error Codes: BadIndex
- In *MatrixView* Bad(RC)Index is used to indicate repeated index.
I have removed BadIntedIndex, BadDegIndex, BadCo...
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...
-
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... -
17:08 Design #427: Error names and error messages (current design)
- Changed Not... into
ReqNonNegative, ReqNonNegativeGrading, ReqPositive, ReqPositiveGrading
and quite a few
@CoCo... -
17:07 Design #308: Error: ERR::NotNonZero instead of ERR::ZeroRingElem? [--> ReqNonZero]
- > > JAA thinks that @LogZero@ should be merged with @NotNonZero@.
done -
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, ... -
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...
Also available in: Atom