Project

General

Profile

Design #1144

File names, coding conventions: Fns, Ops, Operations? part 1

Added by Anna Maria Bigatti over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Renaming
Target version:
Start date:
18 Dec 2017
Due date:
% Done:

100%

Estimated time:
3.01 h
Spent time:

Description

We have used different styles:
MatrixOperations, HomomorphismFns, RegisterServerOps

unify style.


Related issues

Related to CoCoALib - Design #1145: File names, coding conventions: Fns, Ops, Operations? part 2Closed2017-12-19

Related to CoCoALib - Design #1607: Coding guidelinesNew2021-08-03

History

#1 Updated by Anna Maria Bigatti over 6 years ago

  • Category set to Renaming
  • Status changed from New to In Progress
  • Target version set to CoCoALib-0.99600
  • % Done changed from 0 to 10

My preferred is Ops.
I would change for 0.99560 only the new file HomomorphismFns, and postpone the other choice (Ops or Operations) to 0.99570.

#2 Updated by Anna Maria Bigatti over 6 years ago

  • Subject changed from File names, coding conventions: Fns, Ops, Operations? to File names, coding conventions: Fns, Ops, Operations? part 1
  • % Done changed from 10 to 100
  • Estimated time changed from 2.00 h to 3.01 h

HomomorphismFns renamed into HomomorphismOps: changed H,C,doc, makefiles, example, test in cocoalib and cocoa5.

John renamed SparsePolyOps_XXX into SparsePolyOps-XXX

done (the new files) for 0.99560/5.2.2, the rest (the old files) for 0.99570/5.2.4

#3 Updated by Anna Maria Bigatti over 6 years ago

  • Status changed from In Progress to Closed
  • Target version changed from CoCoALib-0.99600 to CoCoALib-0.99560

#4 Updated by Anna Maria Bigatti over 6 years ago

  • Related to Design #1145: File names, coding conventions: Fns, Ops, Operations? part 2 added

#5 Updated by Anna Maria Bigatti almost 3 years ago

Also available in: Atom PDF