Project

General

Profile

Design #1177

File names: use "SparsePolyOps" prefix for pertinent files

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

Status:
Closed
Priority:
Normal
Category:
Various
Target version:
Start date:
06 Apr 2018
Due date:
% Done:

100%

Estimated time:
6.66 h
Spent time:

Description

Use of a prefix is a convenient way to mimick subdirectories.


Related issues

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

Related to CoCoALib - Design #1163: Split SparsePolyRing.C in smaller filesClosed2018-02-27

Related to CoCoALib - Design #1184: should BeginIter(RingElem) be in SparsePolyIter or in SparsePolyOps-RingElem?Closed2018-05-18

Related to CoCoALib - Design #572: Split SparsePolyRing.H into two files? Problem with circular includes.New2014-06-14

Related to CoCoALib - Design #1213: Create PolyOps-RingElem?New2018-08-06

History

#1 Updated by Anna Maria Bigatti almost 6 years ago

  • Assignee set to Anna Maria Bigatti
  • % Done changed from 0 to 30

Now we have

SparsePolyOps-IdealOfPoints
SparsePolyOps-MinPoly
SparsePolyOps-MonomialIdeal
SparsePolyOps-RadicalMembership
SparsePolyOps-RealRadical
SparsePolyOps-ReductionCog
SparsePolyOps-SturmSeq 
SparsePolyOps-geobucket
SparsePolyOps-hilbert
SparsePolyOps-ideal
SparsePolyOps-implicit
SparsePolyOps-involutive
SparsePolyOps-reduce
SparsePolyOps

Now I'm undecided it is write for ReductionCog and geobucket because these actually name a class.

#2 Updated by Anna Maria Bigatti almost 6 years ago

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

#3 Updated by Anna Maria Bigatti almost 6 years ago

  • Status changed from New to In Progress
  • % Done changed from 30 to 50

(split SparsePolyOps-RingElem)

SparsePolyOps-EvalInterval.C*
SparsePolyOps-IdealOfPoints.C*
SparsePolyOps-IdealZeroDim.C*
SparsePolyOps-MinPoly.C*
SparsePolyOps-MonomialIdeal.C*
SparsePolyOps-RadicalMembership.C*
SparsePolyOps-RealRadical.C*
SparsePolyOps-RingElem.C*
SparsePolyOps-RingHom.C*
SparsePolyOps-SturmSeq.C*
SparsePolyOps-hilbert.C*
SparsePolyOps-ideal.C*
SparsePolyOps-implicit.C*
SparsePolyOps-involutive.C*
SparsePolyOps-reduce.C*
SparsePolyOps.C*

#4 Updated by Anna Maria Bigatti almost 6 years ago

  • % Done changed from 50 to 60

I think the content of SparsePolyOps.C (the original ;-) should be now moved into SparsePolyOps-RingElem.C because it conteins 5 functions on RingElem:

  RingElem CoeffHeight(ConstRefRingElem f);

  bool IsPalindromic(ConstRefRingElem f); // univariate only
  RingElem reverse(ConstRefRingElem f); // univariate only
  RingElem reverse(ConstRefRingElem f, ConstRefPPMonoidElem t);

  RingElem graeffe(ConstRefRingElem f);
  RingElem graeffe3(ConstRefRingElem f);

#5 Updated by Anna Maria Bigatti over 5 years ago

  • Related to Design #1163: Split SparsePolyRing.C in smaller files added

#6 Updated by Anna Maria Bigatti over 5 years ago

  • Related to Design #1184: should BeginIter(RingElem) be in SparsePolyIter or in SparsePolyOps-RingElem? added

#7 Updated by Anna Maria Bigatti over 5 years ago

  • Related to Design #572: Split SparsePolyRing.H into two files? Problem with circular includes. added

#8 Updated by John Abbott over 5 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 60 to 100
  • Estimated time set to 6.66 h

#9 Updated by John Abbott over 5 years ago

Also available in: Atom PDF