Project

General

Profile

Design #1807

Error codes: "Not..." for "blah must be ..." -- change prefix

Added by Anna Maria Bigatti 3 months ago. Updated 5 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
Renaming
Target version:
CoCoALib-0.99880
Start date:
26 Mar 2024
Due date:
% Done:

10%

Estimated time:
Spent time:
0.25 h

Description

In the general picture of improving the error codes, I suggest a trivial (though extensive) change.
Look at these names (just a few)

    NotFreeModule
    NotFullRank
    NotNonZero

We have many times discussed that from the code/name of the error it's not obvious if you want the object to be, say, full rank or the opposite.
I propose to change such codes into
ReqFreeModule
ReqFullRank
ReqNonZero

Related issues

Related to CoCoALib - Feature #385: Design new errors using inheritanceIn Progress2013-07-08

History

#1 Updated by John Abbott 3 months ago

  • Related to Feature #385: Design new errors using inheritance added

#2 Updated by John Abbott 5 days ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

Anna proposed this about 3 months ago. We spoke today by phone.
It is reasonable to change the internal error codes so that they begin with Req... rather than Not since the Not prefix can produce some awkward names e.g. NotNonNegative... err what? ReqNonNegative is easier to comprehend.

Anna plans to make this change soon: probably mindless but also mindnumbing. Good luck!

Also available in: Atom PDF