Design #1145
File names, coding conventions: Fns, Ops, Operations? part 2
Description
We have used different styles:
MatrixOperations, RegisterServerOps
choose and rename
Related issues
History
#1 Updated by Anna Maria Bigatti over 6 years ago
- Related to Design #1144: File names, coding conventions: Fns, Ops, Operations? part 1 added
#2 Updated by John Abbott about 6 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
JAA has a preference for Ops
rather than Operations
. I think they are equally clear, and see no advantage in using the longer version.
#3 Updated by Anna Maria Bigatti about 6 years ago
- Related to Design #1177: File names: use "SparsePolyOps" prefix for pertinent files added
#4 Updated by Anna Maria Bigatti almost 6 years ago
- Related to Support #847: Doc for BigInt, BigIntOps, BigRat -- should there be BigRatOps? added
#5 Updated by Anna Maria Bigatti almost 6 years ago
- Status changed from In Progress to Feedback
- Assignee set to John Abbott
- % Done changed from 10 to 90
Confirmed decision: Ops.
#6 Updated by Anna Maria Bigatti almost 6 years ago
- Related to Design #410: New file: BigRatOps added
#7 Updated by Anna Maria Bigatti almost 6 years ago
- Related to Design #408: Rename MatrixArith to MatrixOperations added
#8 Updated by Anna Maria Bigatti almost 6 years ago
renamed MatrixOperations
in MatrixOps
renamed VectorOperations
in VectorOps
#9 Updated by Anna Maria Bigatti almost 6 years ago
renamed IntOperations
into BigIntOps
#10 Updated by John Abbott almost 6 years ago
I have renamed the doc files too.
#11 Updated by John Abbott over 5 years ago
- Status changed from Feedback to Closed
- % Done changed from 90 to 100
- Estimated time set to 3.33 h
*FINAL DECISION: we use the abbreviation Ops
for "operations"
to avoid overly large source code files.
All files have been renamed; in some cases they have been split using a minus sign after @Ops
#12 Updated by Anna Maria Bigatti over 2 years ago
- Related to Design #1607: Coding guidelines added