Activity
From 17 Oct 2019 to 15 Nov 2019
14 Nov 2019
- 19:22 Design #982: Catching interrupts in example progs?
- I have modified @ex-empty.C@ so that it creates a @SignalWatcher@ immediately after @GlobalManager@, and also has a h...
- 19:17 Bug #1362: GBasis verbose mode: some output is on cerr/clog
- I have mostly fixed this. There are also very many commented out debugging prints to clog. Some I have removed; but...
- 09:49 Bug #1362 (In Progress): GBasis verbose mode: some output is on cerr/clog
- In *@TmpGReductor.C@* there are numerous print commands onto *@clog@*; the commands are called only after checking *@...
- 15:28 Feature #1360 (In Progress): configure script: add flags for "only cocoalib" or "both cocoalib and cocoa5" (for boost)
- JAA prefers to delay this so there is time to make more checks...
13 Nov 2019
- 14:59 Bug #1362 (Closed): GBasis verbose mode: some output is on cerr/clog
- With @VerbosityLevel@ set to 150, some output when computing a gbasis is on stderr instead of stdout: _e.g._...
12 Nov 2019
- 14:48 Bug #1361 (Closed): Compilation fails when compiling with libgsl
- If I compile cocoalib 0.99601 with libgsl (version 2.6-1) using:...
05 Nov 2019
- 14:26 Design #982: Catching interrupts in example progs?
- On my machine all examples are faster than 5s, but several took more than 2s.
I have made some (local) changes to ma... - 11:49 Design #982 (In Progress): Catching interrupts in example progs?
- There are two example progs for interrupts (*@ex-interrupt1.C@* and *@ex-interrupt2.C@*).
I am not sure that they ar...
04 Nov 2019
- 11:01 Feature #1360: configure script: add flags for "only cocoalib" or "both cocoalib and cocoa5" (for boost)
- John Abbott wrote:
> Anna suggested *@--only-cocoalib@*
>
> JAA prefers that the default be "only cocoalib", and ...
01 Nov 2019
- 10:28 Feature #1360: configure script: add flags for "only cocoalib" or "both cocoalib and cocoa5" (for boost)
- Anna suggested *@--only-cocoalib@*
JAA prefers that the default be "only cocoalib", and that an option must be giv... - 10:22 Feature #1360 (Closed): configure script: add flags for "only cocoalib" or "both cocoalib and cocoa5" (for boost)
- Considering adding configuration option(s) to specify:
* compile just cocoalib
* compile cocoalib and also also CoC...
31 Oct 2019
- 18:34 Support #1276: Release 0.99650
- ...
- 16:24 Support #1276: Release 0.99650
- Valgrind OK...
- 15:55 Bug #1248 (Closed): MinPolyQuot: guaranteed and ideal without GBasis
30 Oct 2019
- 22:39 Slug #952 (Closed): GCD very slow
- It is no longer very slow; no sure how fast it is (seems to be instant).
Closing.
- 22:32 Bug #986: GFan: require version newer than 0.6
- *2019-10-30* Update: I now have gfanlib-0.6.2 (released 2018-09-28 according to GFanlib website).
However it sti... - 22:23 Slug #1359: gcd: low degree but big coeffs can be slow
- If the number of steps in the PRS is very small then a direct method may well be better than the modular method.
T... - 22:21 Slug #1359 (New): gcd: low degree but big coeffs can be slow
- gcd of low degree polys with big coeffs can be too slow....
- 22:16 Bug #1113 (Closed): gcd crashes (Floating point exception)
- *2019-10-30* I have just tried the example in comment 1, and it no longer crashes. No idea when it was resolved.
... - 22:10 Feature #1218 (In Progress): 32-bit or 64-bit preprocessor macro?
- Exactly what wordsize assumptions do we want to make?
* *(A)* 32-bits or not (meaning more than 32?)
* *(B)* 32-... - 21:56 Feature #1218: 32-bit or 64-bit preprocessor macro?
- *2019-10-30* I have just checked, and CoCoALib and CoCoA-5 both compile, run and all tests pass on my little 32-bit m...
- 21:51 Feature #1219: Frobby version number
- There was recent email from Bjarke Roune stating that he will no longer be able to maintain Frobby.
We should contac... - 21:47 Feature #1282: subresultant
- Note that there is already *@SubresultantSeq@* in @SparsePolyOps-resultant@.
Where did this impl come from? Is it a... - 21:44 Slug #1324 (In Progress): Improve RootBound
- Here is a family of examples where factorization may not work so well:
let @f@ be a product of @x^k-1@ where the @k@... - 11:08 Support #1276: Release 0.99650
- FWIW I have compiled CoCoALib on my old "netbook" which is 32-bit. All tests passed.
29 Oct 2019
- 19:44 Feature #1347 (Closed): New function: ctor of PPVector with vector<RingElem>
- Documented (and modernized its doc file)
- 16:21 Feature #1332 (Closed): New function: vector of RingElem from string -- in CoCoALib
- documented in @RingElem.txt@
- 12:37 Feature #658: Indets actually in a poly (or vector or matrix)
- Checked in @IndetsIn(vector<RingElem>)@
- 12:04 Design #1355 (New): TmpLDP uses srand and time
- The code in *@TmpLDP.C@* uses old C functions *@time@* and *@srand@*.
Try to update the code to clean, modern C++.
- 12:00 Design #1295 (Closed): Never use "using namespace .." in header files
- I must have done this some time ago; no doubt shortly after it was reported.
I have just removed some @using names... - 10:58 Support #1353: configure script help
- I have another suggestion: add the flag *@--only-lib@* that does @--no-boost --no-readline@ and does not compile coc...
28 Oct 2019
- 12:31 Support #1353: configure script help
- Ahhh. I see your point.
For CoCoALib the option *@--no-boost@* does nothing (since CoCoALib does not use BOOST, I... - 11:48 Support #1353: configure script help
- I think that @--no-boost@ should be listed as a CoCoALib option, because it can compile without boost, instead of a C...
27 Oct 2019
- 21:16 Support #1353 (In Progress): configure script help
- I have just compiled CoCoALib with the option *@--no-boost@*, and everything worked fine (as I expected/hoped). Of c...
- 21:13 Support #1353 (Closed): configure script help
- Bruns recently asked (by email) if configuring CoCoALib with *@--no-boost@* will work OK.
I believe CoCoALib does ... - 21:10 Slug #792 (In Progress): configure: search for libgmp too slow
- I think this may already be almost done. Let's finish it soon!
- 21:06 Support #976: configure: auxiliary scripts should be consistent about error messages
- Let's finish this soon! Boosted priority, and brought target version forward.
I think it is almost done anyway... b...
24 Oct 2019
- 15:38 Feature #1349: ideal ctor where given gens are a gbasis
- Here is the background for my request.
I want to modify @MinPolyQuot@ so that it accepts "relatively zero-dim idea... - 15:27 Feature #1349 (In Progress): ideal ctor where given gens are a gbasis
- I would like to create a new ideal from a list which I know is a (reduced) GBasis.
How should I do this?
In fact,... - 15:00 Feature #658: Indets actually in a poly (or vector or matrix)
- I have just added (in @SparsePolyOps-RingElem.C@) an impl for @IndetsIn(const std::vector<RingElem>&)@.
The result i...
21 Oct 2019
- 18:50 Feature #1347 (Feedback): New function: ctor of PPVector with vector<RingElem>
- Done, tested, cvs-ed.
To do: documentation. - 18:49 Feature #1347 (Closed): New function: ctor of PPVector with vector<RingElem>
- While updating the code for monomial ideals using the new range-based for loop I realized how many times I need to in...
- 18:45 Design #1346 (In Progress): C++14: use the new for loop syntax where appropriate (like cocoa's foreach)
- 18:44 Design #1346: C++14: use the new for loop syntax where appropriate (like cocoa's foreach)
- used massively for monomial ideals.
Tested.
cvs-ed. - 12:27 Design #1346: C++14: use the new for loop syntax where appropriate (like cocoa's foreach)
- We should maintain a list of files to change and/or a list of files already changed.
* @SparsePolyOps-ideal-monomial... - 12:26 Design #1346 (In Progress): C++14: use the new for loop syntax where appropriate (like cocoa's foreach)
- Since C++11 there is a new "range-based" *@for@* loop.
Employ it where appropriate in CoCoALib. - 12:29 Design #1242: C++14: Use type auto where appropriate
- I have created a new issue (#1346) about using the new *@for@* loop syntax; please put relevant progress reports ther...
- 12:06 Design #1242: C++14: Use type auto where appropriate
- John Abbott wrote:
> * use *@auto@* instead of the explicit type for C++ iterators (usu. the explicit type is "unrea...
19 Oct 2019
- 20:28 Bug #1345: Problem with linking the library
- John Abbott wrote:
> If you were running your tests from a @cocoa5@ session, then you should also check with @ls -l@... - 19:43 Bug #1345: Problem with linking the library
- Very strange. I think I may have seen a similar phenomenon occasionally, but @make clean; make@ always seemed to fix...
- 17:14 Bug #1345 (Closed): Problem with linking the library
- My mistake?
I tried again, and I cannot longe reproduce it.
It is linked correctly.
- 11:43 Bug #1345 (Closed): Problem with linking the library
- I was testing a change made in @SparsePolyOps-ideal-monomial.C@, and, though it did recompile the file, the new code ...
18 Oct 2019
- 17:04 Design #1242 (In Progress): C++14: Use type auto where appropriate
- 11:23 Design #1242: C++14: Use type auto where appropriate
- It may be helpful to keep a list of source files which have been "done" (this may also include that the file was look...
- 11:19 Design #1242: C++14: Use type auto where appropriate
- I must re-read the relevant parts of Meyers's book (Eff. Modern C++). Where should we use *@auto@*?
* use *@auto@* ... - 16:16 Feature #1332 (Feedback): New function: vector of RingElem from string -- in CoCoALib
- done, documented, tested
17 Oct 2019
- 23:27 Support #1263: Tidy CoCoALib test directory
- I have merged several tests in the series @test-NumTheory@ and @test-SparsePolyRing@ into fewer files.
I have prefer... - 23:23 Feature #1297 (Closed): New fn: FixedDivisor (formerly IntrinsicContent)
- I have added a test (and also reorganized several of the existing tests).
Closing.
- 17:45 Feature #1332: New function: vector of RingElem from string -- in CoCoALib
- OK for the name *@RingElems@* it is a bit like *@symbols@*
(I do not really like it that much, but cannot think of ...
Also available in: Atom