Activity
From 26 Apr 2018 to 25 May 2018
22 May 2018
- 18:00 Support #847: Doc for BigInt, BigIntOps, BigRat -- should there be BigRatOps?
- John Abbott wrote:
> I have split @BigRat@ into @BigRat@ (class defn, ctors, and accessors) and @BigRatOps@.
> All ... - 16:35 Support #847 (Feedback): Doc for BigInt, BigIntOps, BigRat -- should there be BigRatOps?
- I have split @BigRat@ into @BigRat@ (class defn, ctors, and accessors) and @BigRatOps@.
All files have been updated;...
18 May 2018
- 19:02 Design #1177 (In Progress): File names: use "SparsePolyOps" prefix for pertinent files
- (split SparsePolyOps-RingElem)
SparsePolyOps-EvalInterval.C*
SparsePolyOps-IdealOfPoints.C*
SparsePolyOps-IdealZ... - 18:33 Slug #1181: CpuTime is costly!
- Here is a brief comment about the design: I shall suppose that the class is called @CpuTimeLimit@
*(1)* simple us... - 17:52 Design #1184 (Closed): should BeginIter(RingElem) be in SparsePolyIter or in SparsePolyOps-RingElem?
- 17:12 Design #1145: File names, coding conventions: Fns, Ops, Operations? part 2
- renamed @IntOperations@ into @BigIntOps@
- 17:10 Support #847: Doc for BigInt, BigIntOps, BigRat -- should there be BigRatOps?
- Renamed @IntOperations@ into @BigIntOps@
(this should have been in #1145)
17 May 2018
- 18:11 Design #1145: File names, coding conventions: Fns, Ops, Operations? part 2
- renamed @MatrixOperations@ in @MatrixOps@
renamed @VectorOperations@ in @VectorOps@ - 17:58 Slug #1181: CpuTime is costly!
- I now have a prototype which works well in one small test.
The new design does not mimic the old interface... :-/
- 16:35 Design #1163: Split SparsePolyRing.C in smaller files
- Split @SparsePolyIter.H@
(no corresponding C file: only class definition and inline functions)
16 May 2018
- 17:09 Design #410 (In Progress): New file: BigRatOps
- 16:58 Design #1145 (Feedback): File names, coding conventions: Fns, Ops, Operations? part 2
- Confirmed decision: *Ops*.
- 15:48 Feature #1169: New function: RandomLinearForm (CoCoALib)
- John Abbott wrote:
> Probably there should also be a version with interface: *@RandomLinearForm(P, RndSeq)@* where @... - 15:02 Feature #1169: New function: RandomLinearForm (CoCoALib)
- I have added @RandomLinearForm@ to documentation for @SparsePolyRing@.
Probably there should also be a version wit... - 15:46 Support #847: Doc for BigInt, BigIntOps, BigRat -- should there be BigRatOps?
- Good!! go for it! :-)
- 14:07 Support #847 (In Progress): Doc for BigInt, BigIntOps, BigRat -- should there be BigRatOps?
- I like the name @BigIntOps@. The file does also contain several fns which accept @MachineInt@ args (and several whic...
- 13:57 Design #1182 (Resolved): "mod" for BigInt
- I have improved the documentation about @operator%@ by saying that its sign is the same as that of the quotient, and ...
06 May 2018
- 21:51 Design #1182: "mod" for BigInt
- A quick look on the internet suggests that @a%b@ is uniquely defined only if @a@ is non-negative and @b@ is positive;...
05 May 2018
- 19:07 Design #1182: "mod" for BigInt
- John Abbott wrote:
> There is documentation for *@operator%@* in the file @IntOperations.html@. There it points out... - 16:48 Design #1182: "mod" for BigInt
- There is documentation for *@operator%@* in the file @IntOperations.html@. There it points out the existence of two ...
04 May 2018
- 19:29 Design #1182: "mod" for BigInt
- hmmm, I had a negative n, I didn't think of the different behaviour with negative entries.
I suppose I need to read ... - 19:21 Design #1182: "mod" for BigInt
- Wait! I need to make a check....
- 19:12 Design #1182 (Closed): "mod" for BigInt
- n % m, with n,m BigInt gives negative values.
Whether this is reasonable when working in FFp, I find it odd for BigI... - 19:08 Support #847: Doc for BigInt, BigIntOps, BigRat -- should there be BigRatOps?
- Should it be @BigIntOps@?
Also available in: Atom