Design #1163
Split SparsePolyRing.C in smaller files
Status:
Closed
Priority:
Normal
Assignee:
Category:
Renaming
Target version:
Description
The file is now too long.
Split off code for ideals and for involutive operations,
and whatever can be usefully be separated.
(this should make it easier to maintain, and faster to compile)
Related issues
History
#1
Updated by Anna Maria Bigatti about 6 years ago
Updated by - Related to Design #572: Split SparsePolyRing.H into two files? Problem with circular includes. added
#2
Updated by Anna Maria Bigatti about 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 60
- Estimated time set to 3.00 h
#3
Updated by Anna Maria Bigatti almost 6 years ago
Split SparsePolyIter.H
(no corresponding C file: only class definition and inline functions)
#4
Updated by Anna Maria Bigatti almost 6 years ago
- Description updated (diff)
#5
Updated by Anna Maria Bigatti over 5 years ago
- Related to Design #1177: File names: use "SparsePolyOps" prefix for pertinent files added
#6
Updated by Anna Maria Bigatti over 5 years ago
- Status changed from In Progress to Closed
- % Done changed from 60 to 100
Effectively solved. Mostly with SparsePolyOps-xxx files (issue #1177)
#7
Updated by Anna Maria Bigatti over 5 years ago
- Related to Design #1184: should BeginIter(RingElem) be in SparsePolyIter or in SparsePolyOps-RingElem? added