Activity
From 10 Dec 2015 to 08 Jan 2016
06 Jan 2016
- 14:40 Slug #837: factor is very slow on some simple input polynomials
- My "fast" machine in Kassel takes more than 60000s for @x^780+780@, and 1333s for @x^988+988@.
In comparison all pol... - 14:32 Slug #837 (New): factor is very slow on some simple input polynomials
- The problem lies in CoCoALib, but for simplicity I present it here as CoCoA-5 code.
@factor(x^780+780)@ is very sl...
23 Dec 2015
- 12:25 Bug #784: threadsafety: Scott Meyers's advice about cached values
- I read a bit in Stroustrup C++ book. There I found a method @std::call_once@ (in @<mutex>@). This method could be a n...
18 Dec 2015
- 16:26 Feature #664 (Resolved): Impl small non-prime finite fields (using logs)
- I have checked in the code I currently have. no doc, no examples, no tests.
An unofficial, simple example (@Fq4.C@ ...
17 Dec 2015
- 16:25 Design #64: submat takes only vector<long>
- John Abbott wrote:
> If we were to adopt the idea of @RowSelect@ and @ColSelect@ then we could offer several signatu... - 16:07 Design #64: submat takes only vector<long>
- If we were to adopt the idea of @RowSelect@ and @ColSelect@ then we could offer several signatures for @submat@:
* @... - 14:33 Design #64: submat takes only vector<long>
- John Abbott wrote:
> Here are some other possible suggestions:
I think that's too many, and I think it's not wort... - 16:19 Feature #664: Impl small non-prime finite fields (using logs)
- JAA now has a prototype impl which still needs lots of cleaning, but some simple tests pass :-)
I'm hoping to clea...
16 Dec 2015
- 18:23 Design #64: submat takes only vector<long>
- Scott Meyers advises making interfaces which are "easy to use correctly and hard to use incorrectly"; I think this is...
- 18:11 Design #64 (In Progress): submat takes only vector<long>
- Here are some other possible suggestions:
* @submat(M, AllRows, ...)@ to select just certain columns
* @submat(M, .... - 11:42 Design #64: submat takes only vector<long>
- I don't think we should allow other integer types, after all we want to discourage other integer types.
One think I ... - 11:52 Design #825: IsPositiveGrading -- really need 2 signatures?
- -- fixed test anna.cocoa5
-- updated CoCoA-5 manual
-- made suggestion for submat ;-)
10 Dec 2015
- 18:19 Feature #836 (Feedback): SmallFpImpl: export fns for a fixed convention
- It was quite trivial to add the new fns. I have updated the doc too.
Should there be a specific test?
Should imp... - 18:16 Feature #836 (Closed): SmallFpImpl: export fns for a fixed convention
- I found a case where I needed to obtain the least non-negative residue from a @SmallFpImpl::value@. Doing this via @...
- 15:59 Bug #834: Fix test failures (after revising MatrixForOrdering)
- Ignoring the question of the name for @ColCheck@, is it better to have a single fn with a flag to say whether or not ...
- 15:03 Bug #834: Fix test failures (after revising MatrixForOrdering)
- I'm also writing *@IsUpperTriangular@*.
*Addendum* (JAA) also @IsLowerTriangular@? Will these go into a "matrix" so... - 14:36 Bug #834: Fix test failures (after revising MatrixForOrdering)
- I'm writing another function *HasNegEntry* which checks whether there is a negative entry.
(then we can think of a be... - 13:11 Bug #834: Fix test failures (after revising MatrixForOrdering)
- lines 304 and following (@#ifdef@) in @PPOrdering.C@ should be deleted:
we do non require to have a PositiveGrading f... - 10:17 Bug #834: Fix test failures (after revising MatrixForOrdering)
- I have just checked in a modified version of @MatrixForOrdering.C@ following Anna's suggestion in comment 2.
Now "...
Also available in: Atom