Support #1510
Documentation for SparsePolyOps?
Start date:
14 Oct 2020
Due date:
% Done:
30%
Estimated time:
Description
Where should the doc for fns in SparsePolyOps-* files go?
The current organization is inconsistent :-(
Related issues
History
#1
Updated by John Abbott over 2 years ago
Updated by - Related to Feature #1488: BuiltIn Interreduce-Function added
#2
Updated by John Abbott about 2 years ago
- Target version changed from CoCoALib-0.99800 to CoCoALib-0.99850
#3
Updated by John Abbott about 1 year ago
- Related to Support #1265: Unregistered TXT files in doc added
#4
Updated by Anna Maria Bigatti about 2 months ago
Updated by - Related to Design #1783: Code & doc structure: one-big-file or many-small-files? added
#5
Updated by John Abbott about 1 month ago
- Target version changed from CoCoALib-0.99850 to CoCoALib-0.99880
#6
Updated by Anna Maria Bigatti about 1 month ago
- Target version changed from CoCoALib-0.99880 to CoCoALib-0.99850
See #1783-2 : one doc file for each topic/file
#7
Updated by Anna Maria Bigatti about 1 month ago
- Target version changed from CoCoALib-0.99850 to CoCoALib-0.99880
- % Done changed from 0 to 30
The SparsePolyOps files are quite focused on a specific topic.
Doc would be easier to maintain if kepts separately.
However, some functions should be much easier to FIND if in a single file (see RingElem.txt).
We need to define properly how to deal with these aspects.