Activity
From 21 Jun 2024 to 20 Jul 2024
15 Jul 2024
- 18:20 Bug #1824: (easy?) Problem in myGBasis_EasyCases
- Here is a copy of the failing example:...
- 17:15 Design #427: Error names and error messages (current design)
- > I have tried copying it in
> @#define CoCoA_THROW_ERROR1(ErrID)@
> for when we do not need the extra details, an... - 11:23 Design #427: Error names and error messages (current design)
- John made a big step forward (quite possibly the final design) with the macro
@#define CoCoA_THROW_ERROR2(ErrID, Mor...
14 Jul 2024
- 12:51 Bug #1824 (In Progress): (easy?) Problem in myGBasis_EasyCases
- I was careless before: it is good that the assertion there, because it is reporting that *@IHaveGBasis@* is false but...
- 11:20 Bug #1824: (easy?) Problem in myGBasis_EasyCases
- Is there documentation about how the various data members of an ideal interact?
Anyway, I expect this bug to be easy... - 11:15 Bug #1824 (In Progress): (easy?) Problem in myGBasis_EasyCases
- The exbug 1416 (in CoCoA-5/tests/exbugs.cocoa5) triggers an *@Assertion Failed@*
I think there us a logic error in...
07 Jul 2024
- 12:11 Feature #1793: Use ErrorContext instead of string FnName
- This is better than using a @std::string@ to specify the function name, especially if we want to allow errors/excepti...
03 Jul 2024
- 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...
27 Jun 2024
- 21:28 Feature #743: Better errors: give supplementary info about the error
- This has been _urgent_ for at least 7 years... oops!
Anna's suggestions in comments 21 and 22 are good (and also K... - 21:10 Feature #385: Design new errors using inheritance
- I have just read through all the comments above. The suggestion in comment 14 looks to be a very good start -- I can...
- 20:04 Feature #385: Design new errors using inheritance
- Has this been _urgent_ for the past 11 years? Oops!
- 20:09 Design #1807 (In Progress): Error codes: "Not..." for "blah must be ..." -- change prefix
- Anna proposed this about 3 months ago. We spoke today by phone.
It is reasonable to change the _internal error code...
Also available in: Atom