Activity
From 24 Oct 2020 to 22 Nov 2020
20 Nov 2020
-
15:04 CoCoA-5 Design #1520: Replace BOOST_FOREACH by new C++14 range for syntax
- We still need to see where the new the @for@ syntax can be used in cocoalib -- that is issue #1346.
Maybe I should... -
15:01 CoCoA-5 Design #1520 (Resolved): Replace BOOST_FOREACH by new C++14 range for syntax
- I think I have done most of the code in @src/CoCoA-5@.
It compiles and the CoCoA-5 tests all pass.
I made the chang... -
14:11 CoCoA-5 Design #1540: Double power
- I would like to maintain reasonable compatibility between the way CoCoA-5 parses expressions and the way @RingElem@ o...
-
13:35 CoCoA-5 Feature #500: Interpreter: is it possible to avoid useless prompts?
- Apparently the ability to suppress prompts could be useful for the ApCoCoA interface.
For that application, it wou... -
11:36 CoCoA-5 Bug #1539 (Feedback): Website: installation instructions for Microsoft
-
11:35 CoCoA-5 Bug #1539: Website: installation instructions for Microsoft
- fixed
-
11:27 CoCoA-5 Bug #1539: Website: installation instructions for Microsoft
- What was nice was that Bernhard wrote "shouldn't cocoa-5.2 be cocoa-5.2?"
So even bug reporters can make typos ;-)
-
08:56 CoCoA-5 Design #1530: VersionInfo -- better field names?
- Done.
I added "Boost" only in BuiltinFunctions.C.
I have also the code for adding it in ExternalLibs.C (commented o...
17 Nov 2020
-
22:53 CoCoALib Design #1538 (In Progress): RingElem from string (ReadExpr)
- The input functions are quite messy: not really a coherent design philosophy.
It seems that *@ReadExpr@* gives err... -
22:33 CoCoA-5 Support #322: Installation instructions (on website)
- Last week a student came with some problems with making CoCoA work on her MacBook; most of these are dealt with elsew...
-
20:31 CoCoA-5 Bug #1537: EmacUI: strange colours, sometimes
- A possible way to address the problem is to discourage users from typing *@/-@* by making it issue a warning.
As a... -
20:26 CoCoA-5 Bug #1537: EmacUI: strange colours, sometimes
- This is probably not solvable :-(
I changed the emacs syntax declaration for "minus" into just a plain "." (punctu... -
20:11 CoCoA-5 Bug #1537: EmacUI: strange colours, sometimes
- Here is some doc about emacs;...
-
20:02 CoCoA-5 Bug #1537: EmacUI: strange colours, sometimes
- Around line 335 in @cocoa5.el@ there is this...
-
19:48 CoCoA-5 Bug #1537: EmacUI: strange colours, sometimes
- As far as I can tell the following "digraphs" are recognized as starting a comment:
slash-star, slash-slash, slash-m... -
13:49 CoCoA-5 Bug #1537 (In Progress): EmacUI: strange colours, sometimes
- I have tried a few tests. slash-minus seems to be recognised as a comment start; I have tried slash-char where char w...
-
13:19 CoCoA-5 Design #1540 (In Progress): Double power
- If we do look at handling exponents, it might be nice to improve the error mesg when a negative exponent is given wit...
16 Nov 2020
-
18:07 CoCoA-5 Design #1540: Double power
- I think CoCoA should give a warning or even an error. Currently, it gives neither!
On my computer I got *@x^8@*
... -
18:05 CoCoA-5 Design #1540 (Closed): Double power
- What do you think CoCoA does with the following input?...
-
09:43 CoCoA-5 Bug #1539 (Closed): Website: installation instructions for Microsoft
- The installation instructions for Microsoft refer to the directory *@C:\cocoa-5.2\emacs@* instead of *@C:\cocoa-5.3\e...
13 Nov 2020
-
18:29 CoCoALib Design #1391: RingElems: syntax with [ and ] ?
- The C++ version does not work: @WhatsNext@ causes too much trouble :-(
Groan... -
14:36 CoCoALib Design #1391: RingElems: syntax with [ and ] ?
- Remove the CoCoA-5 and make it call the cocoalib version.
-
16:00 CoCoA-5 Design #1530: VersionInfo -- better field names?
- *Anna will do the following*
(1) move the info about BOOST into the subrecord @ExternalLibs@ (_i.e._ added to the li... -
14:34 CoCoA-5 Design #1530: VersionInfo -- better field names?
- and add Boost into the ExternalLibs record
-
15:48 CoCoA-5 Support #1534 (In Progress): Install CoCoA-5 on MacOS-10.15+
- Anna could you do the following on your old MacBook:
(1) download the official distrib
(2) follow the instructions ... -
14:26 CoCoA-5 Support #1534: Install CoCoA-5 on MacOS-10.15+
- I have had trouble installing CoCoA-5 from our website on my old mac.
-
15:20 CoCoALib Design #1538: RingElem from string (ReadExpr)
- My personal opinion is that I do not like *@1/-2@* and *@2*-3@*; they both look like typos to me. Perhaps the user m...
-
15:04 CoCoALib Design #1538: RingElem from string (ReadExpr)
- Similar problem for *@RingElem(QQ, "2*-3");@*
-
14:59 CoCoALib Design #1538 (Closed): RingElem from string (ReadExpr)
- What should the following do...
-
14:48 CoCoA-5 Bug #1537 (Closed): EmacUI: strange colours, sometimes
- ...
-
11:23 CoCoA-5 Feature #1536: Implement xel?
- The matter was raised by Bernhard Andraschko. His argument is below:...
-
11:19 CoCoA-5 Feature #1536 (Closed): Implement xel?
- At the moment CoCoA-5 does not recognise the keyword @xel@ for specifying a term order when defining a new ring.
I...
12 Nov 2020
-
13:47 CoCoA-5 Feature #1535: New functions: argmin, argmax
- Here is a little background/motivation.
I demoed to the students how one can impl in CoCoA-5 the algm to compute a m...
11 Nov 2020
-
15:11 CoCoA-5 Feature #1535: New functions: argmin, argmax
- I clearly prefer @argmin@, since its easier to type and lower-case is also more common in mathematics, but (as for ma...
-
11:25 CoCoA-5 Feature #1535: New functions: argmin, argmax
- What should the names be?
In most contexts they are written @argmin@ (or maybe @arg min@ with a space).
Should be u... -
11:23 CoCoA-5 Feature #1535: New functions: argmin, argmax
- Should this actually be in CoCoALib?
Might it be handy to have a version which returns the index (or indices) of t... -
11:20 CoCoA-5 Feature #1535 (In Progress): New functions: argmin, argmax
- Here is a first prototype in CoCoA-5...
-
11:14 CoCoA-5 Feature #1535 (In Progress): New functions: argmin, argmax
- Proposal:
create new functions @argmin@ and @argmax@ which operate on lists.
The idea is that they return an/all ...
10 Nov 2020
-
19:57 CoCoA-5 Support #1534 (In Progress): Install CoCoA-5 on MacOS-10.15+
- Review the instructions for installing CoCoA-5.3 on MacOS.
Unfortunately it seems that an administrator account an... -
14:11 CoCoALib Feature #1532: Convenient RingHom pseudo-ctors
- It might be possible to extend the impl give above to handle quotients of poly rings, and perhaps also "towers" of po...
-
14:07 CoCoA-5 Bug #1531 (Feedback): CRASH: arithmetic with HilbertSeries (tagged object)
-
13:58 CoCoA-5 Design #1530 (In Progress): VersionInfo -- better field names?
- I suggest for the "Num bits" fields to the names *@NumBits_MachineInt@*, *@NumBits_MachineLong@* and *@NumBits_Small...
09 Nov 2020
-
21:13 CoCoALib Feature #1466: Ops += *= etc for Matrices?
- It is not clear to me how to implement @+=@ etc. better than the naive way, and maintain exception safety.
It migh... -
21:02 CoCoALib Bug #1233: factor SEGV -- too large characteristic
- Revised example (now that we're mostly 64 bit)...
06 Nov 2020
-
14:24 CoCoALib Feature #1532: Convenient RingHom pseudo-ctors
- Florian mentions that Singular has something called *@imap@*...
-
14:07 CoCoALib Feature #1532 (In Progress): Convenient RingHom pseudo-ctors
- Here is a prototype in CoCoA-5... we would also need a version for cocoalib!!...
-
13:20 CoCoALib Feature #1532: Convenient RingHom pseudo-ctors
- Here is the example Florian wanted:...
-
13:14 CoCoALib Feature #1532 (In Progress): Convenient RingHom pseudo-ctors
- CoCoALib should offer some convenient pseudo-ctors for @RingHom@.
One example would be from @QQ[x,y,z]@ into @QQ(x... -
13:56 CoCoA-5 Design #1533: RingElem and IndetSymbols not compatible
- The obvious convenient solution would be to allow @RingElem@ to accept the @RECORD@ produced by @IndetSymbols@.
Migh... -
13:54 CoCoA-5 Design #1533 (In Progress): RingElem and IndetSymbols not compatible
-
13:34 CoCoA-5 Design #1533 (In Progress): RingElem and IndetSymbols not compatible
- The funcrions @RingElem@ and @IndetSymbols@ are sort-of-inverses; but we could perhaps do better?...
05 Nov 2020
-
19:00 CoCoA-5 Bug #1531: CRASH: arithmetic with HilbertSeries (tagged object)
- At least + is commutative: @HilbertSeries(...)+1@ also causes a crash!
I have modified @Interpreter.C@, and checked ... -
15:12 CoCoA-5 Bug #1531: CRASH: arithmetic with HilbertSeries (tagged object)
- I have just tried using my last idea @rightOp->getType()->isProperSybstypeOf(..)@.
It compiled, and now produces a v... -
15:07 CoCoA-5 Bug #1531 (In Progress): CRASH: arithmetic with HilbertSeries (tagged object)
- The troublesome call is on line 1536 of @Interpreter.C@.
The problem is that @rightType@ has @dispatchIndex@ equal t... -
14:41 CoCoA-5 Bug #1531 (Closed): CRASH: arithmetic with HilbertSeries (tagged object)
- The following input causes an assertion failure, followed by abort:...
04 Nov 2020
-
20:41 CoCoALib Design #1529: INPUT questions
- One mild concern is that the reading fns in C++ try to accept the maximum length initial string which gives "valid" i...
-
20:25 CoCoALib Design #1529 (In Progress): INPUT questions
- The code for reading a @BigRat@ can read it either as a fraction @N/D@ or as a decimal @Int.frac@.
For the "decima... -
20:06 CoCoALib Design #1529: INPUT questions
- Ooops! I have had a look a what happens when a @BigInt@ is read... and I found a bug :-(
For @BigInt@ no space is... -
17:41 CoCoALib Design #1529: INPUT questions
- Regarding point *(1)*... what should input of a @BigRat@ do with the following input streams?
* *@1/2@* -->JAA: ... -
17:33 CoCoALib Design #1529: INPUT questions
- One possibility would be to require that an integer literal start with a decimal digit: _e.g._ there is no problem in...
-
13:35 CoCoALib Slug #1517: RandomLinearForm
- I presume the timings in comment 4 were with @unsigned short@ as @SmallExponent_t@ (otherwise CoCoA has suddenly beco...
-
12:30 CoCoA-5 Design #1530: VersionInfo -- better field names?
- I would like @VersionInfo@ to tell me also how many bits are in @SmallExponent_t@ (since this does seem to affect exe...
-
12:28 CoCoA-5 Design #1530 (Closed): VersionInfo -- better field names?
- The order of the fields printed by @VersionInfo@ is alphabetical. This means that some pieces of info are ordered st...
-
12:25 CoCoA-5 Feature #250: CoCoALib BuildInfo vs CoCoA-5 VersionInfo
- Is this issue still relevant?
Close? Reject? -
12:06 CoCoA-5 Feature #1479: CoCoA release for linux: CoCoAInterpreter: with and without libreadline?
- Currently the script reports a very succinct error message if the executables cannot run (probably due to shared libr...
-
10:48 CoCoA-5 Bug #1527 (Feedback): Inadequate error message on incorrect list access
- I have checked in the code.
03 Nov 2020
-
22:19 CoCoA-5 Feature #1293: Vim Plugin for CoCoA
- Can we make the link for the imminent (interim) release?
-
22:17 CoCoA-5 Bug #1527: Inadequate error message on incorrect list access
- This is what happens now:...
-
21:12 CoCoA-5 Bug #1527 (Resolved): Inadequate error message on incorrect list access
- I have made a change (by adding a call to mem fn @asRightValue@).
Now the code seems to be doing more or less what I... -
22:11 CoCoA-5 Feature #1479 (Feedback): CoCoA release for linux: CoCoAInterpreter: with and without libreadline?
- Here is a little doc (where should it really go?)
The new script expects one of two possibilities for the @bin/@ d... -
22:03 CoCoA-5 Support #1459 (Closed): Manual entries for mod and div
-
21:03 CoCoALib Slug #897 (Feedback): SimplestBigRatBetween: why is it so slow?
- I have checked in (despite the presence of some experimental changes).
-
20:51 CoCoALib Design #1391 (Feedback): RingElems: syntax with [ and ] ?
- I have implemented *@RingElemVec@*; the code is mostly shared with @RingElems@.
02 Nov 2020
-
22:20 CoCoA-5 Bug #1527: Inadequate error message on incorrect list access
- I do not understand lines 146 and 147 in @AST.H@.
They seem to say that everything can be indexed by both INT and ST... -
22:17 CoCoA-5 Bug #1527: Inadequate error message on incorrect list access
- Na toll:...
-
21:45 CoCoA-5 Bug #1527: Inadequate error message on incorrect list access
- There is a fn *@canBeIndexedByBigInt@*, but there does not seem to be a @canBeIndexedByString@*.
Maybe I should ma... -
21:42 CoCoA-5 Bug #1527: Inadequate error message on incorrect list access
- I have a partial fix: the error mesg now says "Expecting type STRING" if the value being indexed is a @RECORD@ otherw...
31 Oct 2020
-
09:04 CoCoALib Design #1529 (Closed): INPUT questions
- I have some questions about what inputs should be accepted.
*(1)* when reading a @BigRat@ we accept <Integer-liter...
30 Oct 2020
-
20:49 CoCoA-5 Support #1498 (Feedback): Export many names or just one?
- I have changed the impl so that only a single name after @export@ is expected.
Amazingly it compiled first time, and... -
20:20 CoCoALib Design #1523: Input fns: action when when istream is in bad state?
- Checked in, but not @symbol.C@.
-
19:54 CoCoALib Design #1523: Input fns: action when when istream is in bad state?
- The function @symbol::myInput@ reports an error by setting the channel state (@failbit@) rather than throwing an exce...
-
19:46 CoCoALib Design #1523 (Resolved): Input fns: action when when istream is in bad state?
- I have added checks to all input fns so that an exception is thrown if the istream is not in a good state when called...
-
19:24 CoCoALib Design #1523 (In Progress): Input fns: action when when istream is in bad state?
- After discussion with Anna, we have decided that it is more helpful if an exception is thrown if the @istream@ is not...
-
20:20 CoCoA-5 Feature #1509: RingElems with empty input
- Checked in.
-
19:58 CoCoA-5 Feature #1509 (Feedback): RingElems with empty input
- I have also implemented @RingElemVec@ (even though Anna did not want it).
I'll check in so we can test it.
-
16:11 CoCoA-5 Design #1525: CoCoA Manual: homogenize obsolete/obsolescent entries
- Possibly add the year
-
15:59 CoCoALib Slug #1518: SLUG: Printing PPs with many indets
- Anna suggest using a virtual fn for printing which is specialized in PPMs which can have big exps.
JAA will think ... -
15:33 CoCoALib Design #601 (In Progress): LongRange: in which file should it be declared/defined?
- Anna is uneasy about making a header file for just a single function.
Ideally, there could be some other similar fun... -
15:19 CoCoALib Support #861 (Feedback): Janet basis code: TmpJB files give some problems with C++11 (using CLANG/LLVM)
- Anna says it compiled cleanly now.
JAA: must remove the commented out code.
-
15:15 CoCoALib Design #1528 (Closed): MacOS compilation with clang
- Try to clean out clang compilation
-
14:51 CoCoALib Bug #1484: ker bug (quotientinghom for R/ideal())
- For me: test, and add CoCoALib tests
-
12:02 CoCoA-5 Bug #1527 (In Progress): Inadequate error message on incorrect list access
- The relevant function seems to be *@IndexedAccessExpression::implEval@* in @Interpreter.C@ around lines 3677--3695.
... -
10:19 CoCoA-5 Bug #1527 (Closed): Inadequate error message on incorrect list access
- When trying to access a list using another list, the error message seems to be incorrect.
Here is an example:
<pr... -
11:08 CoCoALib Support #1494 (Closed): Normaliz 3.8.9
29 Oct 2020
-
22:03 CoCoA-5 Feature #1509: RingElems with empty input
- I do not think it is dangerous.
We cannot easily compare with C++ input via the @>>@ operator since that reads int... -
15:57 CoCoA-5 Feature #1509: RingElems with empty input
- John Abbott wrote:
> We could add the following at the start of @RingElems@ (in @RingElemInput:C:278@)
> if (in.e... -
21:51 CoCoALib Slug #1170 (Closed): SmoothFactor: slow when a factor is found
- The current impl is acceptable for the time being; out efforts need to be directed elsewhere.
Closing.
-
21:48 CoCoALib Design #1279 (Closed): Tidy up code for matrix determinant
- The current version is acceptable; it could be made better, but there are plenty of other more important issues (at t...
-
21:44 CoCoALib Design #1463 (Closed): SmoothFactor: use FactorMultiplicity
-
21:30 CoCoALib Design #1463: SmoothFactor: use FactorMultiplicity
- I have fixed the bug: part of the code incorrectly assumed that the base was a prime number... ooops! (probably an o...
-
15:13 CoCoALib Design #1463: SmoothFactor: use FactorMultiplicity
- @FactorMultiplicity(3^39,factorial(21))@ goes into infinite loop :-/
It gets worse...
@FactorMultiplicity(9, fact... -
15:10 CoCoALib Design #1463: SmoothFactor: use FactorMultiplicity
- Oh no! I have hit a bug:...
-
21:42 CoCoALib Support #1196 (Closed): Split MatrixOps
- The current situation is acceptable. Further splitting might be a good idea at some point, but it is not so importan...
-
21:36 CoCoALib Feature #1436 (Closed): Flatten for a matrix
-
18:18 CoCoA-5 Design #1525 (In Progress): CoCoA Manual: homogenize obsolete/obsolescent entries
- Done up to letter P
-
17:50 CoCoA-5 Design #1525: CoCoA Manual: homogenize obsolete/obsolescent entries
- This is how the renamed ones should look like...
-
17:04 CoCoA-5 Design #1525: CoCoA Manual: homogenize obsolete/obsolescent entries
- The section "see also" is handy only for the online version.
Remove them.
Think of an easy way to call the manual... -
17:01 CoCoA-5 Design #1525 (Closed): CoCoA Manual: homogenize obsolete/obsolescent entries
- I'm cleaning the manual for a homogeous straightforward style for obsolete/obsolescent entries.
Mainly it should jus... -
17:43 CoCoA-5 Feature #1526 (Closed): EmacsUI: help/manual for selected string -- or just for word with cursor on?
- Make it possible to get the manual for a selected string.
In the file buffer it is C-c C-h and it is also in the m... -
15:01 CoCoALib Design #1460 (Closed): Name of TensorMat; change to KroneckerProd?
- This has been in feedback for a month or so. CLosing:
Conclusion: fn name changed @KroneckerProd@, impl creates n... -
14:52 CoCoALib Slug #1518: SLUG: Printing PPs with many indets
- Here is a guess as to why the observed times are as they are:
with @myBigExponents@ the ctor for @BigInt@ is called ... -
14:47 CoCoALib Design #601: LongRange: in which file should it be declared/defined?
- What about *@utils-LongRange@*?
This name should also make it clear why the file is included.
-
14:43 CoCoALib Slug #1517 (In Progress): RandomLinearForm
- The empirical complexity appears to be quadratic. Here is my test:...
-
14:26 CoCoALib Support #861: Janet basis code: TmpJB files give some problems with C++11 (using CLANG/LLVM)
- Since we are no longer guaranteeing pre-C++11 compatibility, we can remove from Mario's code all @#if@ trickery relat...
-
13:49 CoCoA-5 Support #1498: Export many names or just one?
- This is a marginal issue, but we have two contrasting things (and now we know it ;-) ), so we should make a decision....
-
13:21 CoCoA-5 Support #1498: Export many names or just one?
- The relevant source code is in @Parser.C@ from line 556 to 595.
It is surprisingly long; allowing just a single nam... -
13:46 CoCoALib Design #1465: mul(MAT,MAT,MAT)
- Perhaps it could make sense to have a version of *@mul(mat,mat,mat)@* which is deliberately not exception safe (but a...
-
13:43 CoCoALib Design #1125: Separate install script for CoCoALib?
- Ideally the installation process should also make available an easy way to uninstall the installed stuff.
We also ... -
13:32 CoCoALib Feature #1349: ideal ctor where given gens are a gbasis
- There are already fns *@IdealOfGBasis@* and *@SetGBasisAsGens@*. Where is the doc for the 2nd fn?
Despite some in... -
10:36 CoCoALib Feature #142: Improve threadsafety
- I propose the following new names:
* *@--allow-non-threadsafe@* for the @configure@ script
* *@CoCoA_ALLOW_NON_THRE...
28 Oct 2020
-
23:17 CoCoALib Bug #1331 (Closed): adj: for matrices 7x7 and bigger
-
23:12 CoCoA-5 Bug #1524 (In Progress): wrong SystemCommand exit value
- According to cppreference, the return value of @std::system@ is _implementation defined._
The CoCoA manual was too s... -
09:56 CoCoA-5 Bug #1524 (Closed): wrong SystemCommand exit value
- I just noticed that @SystemCommand@ returns incorrect exit values, in particular the returned value is ´exit_val * 25...
27 Oct 2020
-
19:17 CoCoALib Feature #645 (In Progress): Automatic mapping of RingElem: user selectable at run-time (GlobalManager?)
- At the moment all fns which allow automatic promotion of ringelems call the function *@AutomaticConversionHom@*.
I... -
19:11 CoCoA-5 Design #635 (Resolved): Automatic mapping of RingElem (in operation with a compound value)
- I have changed the impl so that there is no auto promotion for matrices.
The example in comment 1 now gives... -
18:51 CoCoA-5 Design #635: Automatic mapping of RingElem (in operation with a compound value)
- I must change the impl so that only the ringelem gets mapped. To map the matrix one must make an explicit call.
O... -
19:08 CoCoA-5 Feature #1461 (Closed): Automatic mapping for multiplication?
- As suggested in comment 10 above, I have copied the "done list" and the "todo list" to issue #7.
Closing this issue ... -
19:05 CoCoA-5 Feature #7: Automatic mapping between (some) rings
- Here are done list and todo list copied from issue #1461 comments 7 & 8. Moving them here.
*DONE LIST*
* @Matri... -
18:43 CoCoA-5 Feature #7: Automatic mapping between (some) rings
- *I have decided to make this the "master issue" for questions related to automatic ring conversion* (mainly because i...
-
18:40 CoCoA-5 Design #1493 (Feedback): Automatic ring mapping in assignment?
- I have revised the manual entry for @matrix@. I did note that in the examples @mat@ is used rather than @matrix@ -- ...
-
18:15 CoCoA-5 Design #637 (Closed): Undesirable consequence of automatic mapping of RingElems?
- *Conclusion: no automatic mapping of ringelems in equality tests*
A user working in several rings at once has to s... -
18:01 CoCoALib Design #1515 (Rejected): Indets in coeffring are ringelems in coeffring?
- *I am rejecting this because of the example in comment 3 above.*
I have also rejected the duplicate issue #636.
-
17:59 CoCoA-5 Design #636 (Rejected): Distinguish indets from symbols in coeffring in Use command
- I am rejecting this. This issue is essentially duplicated in #1515.
*Main reason for rejection is in comment 3 of... -
15:56 CoCoALib Slug #1518: SLUG: Printing PPs with many indets
- I have just tried again but with @SmallExponent_t@ being @unsigned short@ (previously it was @unsigned int@).
Printi... -
15:21 CoCoALib Slug #1518: SLUG: Printing PPs with many indets
- I have just repeated the experiment, but in CoCoALib. This is the test program:...
-
15:26 CoCoALib Design #1085: Fns with "OUT" args: should they give ERR::MixedRings?
- This issue is a generalized version of issue #1500 (which itself is concerned with the example in comment 1 of this i...
-
10:34 CoCoALib Feature #142: Improve threadsafety
- I changed @SmartPtrIRC@ so that an @std::atomic<std::size_t>@ is used for the ref count instead of @std::size_t@.
I ...
26 Oct 2020
-
21:38 CoCoALib Feature #1483 (Closed): IsPowerOf2 for rationals
-
21:37 CoCoALib Feature #1457 (Closed): Make SmoothFactor interruptible
-
20:20 CoCoALib Slug #1518: SLUG: Printing PPs with many indets
- I have just tried modifying the impl (@PPMonoid.C@ around lines 215--230, @PPMonoidBase::myOutput@).
The modified ve... -
20:06 CoCoALib Slug #1518: SLUG: Printing PPs with many indets
- Here is a reference test:...
-
16:59 CoCoALib Slug #1518 (In Progress): SLUG: Printing PPs with many indets
- I propose the following revision to the design:
* *(A)* each @PPMonoid@ has a fn which says whether it can handle on... -
19:49 CoCoALib Bug #1522: SEGV: avoid long linked lists of loaves in MemPools
- I now think it is probably a good idea to abandon the current design with explicit "NextLoaf" pointers (currently @s...
-
17:07 CoCoALib Bug #1522: SEGV: avoid long linked lists of loaves in MemPools
- I think I have found the cause... it is in "invisible code" written by the compiler. The invisible code is correct, ...
-
14:38 CoCoALib Bug #1522: SEGV: avoid long linked lists of loaves in MemPools
- Ahhh! Perhaps I should have guessed: @valgrind@ reports that the problem is *@stack overflow@*.
Now, why are we usi... -
13:53 CoCoALib Bug #1522: SEGV: avoid long linked lists of loaves in MemPools
- I got a SEGV with debugging on and MemPool disabled. Let's see what valgrind says...
BTW it was even slightly faste... -
13:08 CoCoALib Bug #1522 (In Progress): SEGV: avoid long linked lists of loaves in MemPools
- Triggered by the example from issue #1514.
The SEGV seems to arise during destruction at the end of the program!
... -
13:00 CoCoALib Bug #1522 (Closed): SEGV: avoid long linked lists of loaves in MemPools
- See comment 4 below, where I understand the root cause.
Original report:
I get a SEGV reading about 4500 random l... -
19:45 CoCoALib Feature #142: Improve threadsafety
- I now think that it is probably better to default to threadsafe code; the user must configure with "not threadsafe" t...
-
19:41 CoCoALib Design #1523: Input fns: action when when istream is in bad state?
- If we do follow this recommendation, which files must be considered?
* @RingElemInput@
* @BigInt@ and @BigRat@?
* ... -
14:35 CoCoALib Design #1523: Input fns: action when when istream is in bad state?
- At the moment my preference is to recommend (strongly) that input fns immediately check whether the @istream@ is not ...
-
14:31 CoCoALib Design #1523 (Closed): Input fns: action when when istream is in bad state?
- Output fns in CoCoALib check whether the @ostream@ is in a bad state, and if so, return without doing anything more.
... -
19:39 CoCoA-5 Feature #1509 (Resolved): RingElems with empty input
- I have improved (??) the code. It should give better err mesgs now. Here are some examples:...
-
12:26 CoCoALib Support #1499 (Closed): factorization: allow zero as exponent?
- *FINAL DECISION:*
* do not allow 0 multiplicity (will throw an exception)
* do not allow factorization objects over... -
12:08 CoCoA-5 Bug #1514 (Feedback): Cocoa crashes when calling RingElems
- A temporary workaround for Julian is probably the following:
* obtain the CoCoA sources, modify @include/CoCoA/confi... -
09:56 CoCoA-5 Bug #1514: Cocoa crashes when calling RingElems
- I was not able to get the information I wanted from @valgrind@ (probably my fault).
After some thinking (but less ... -
12:06 CoCoALib Slug #1521: Unexpectedly slow example with larger types for SmallExponent_t
- See note 5 in issue #1514.
-
12:05 CoCoALib Slug #1521 (New): Unexpectedly slow example with larger types for SmallExponent_t
- I tried Julian's example from issue #1514 using smaller types for @SmallExponent_t@, and found that it was significan...
-
11:49 CoCoA-5 Feature #1516: substring function
- The C++ substring function has the following interface:
* @substr(str,n)@ the substring starting at the n-th posn u... -
10:38 CoCoALib Bug #1473: isystem not working as expected
- I have done a little checking.
*The GMP header is automatically C++ safe:* it contains all necessary @extern "C"@ ... -
10:15 CoCoA-5 Design #1508: Initial ring
- Presumably the CoCoA-5 interpreter has a function which performs the command *@source@*. If this function can accept...
-
10:10 CoCoA-5 Design #1519: Interpreter fn Value::from can use std::move?
- The template function for lists (of all sorts) is actually called @LIST::LIST@... mmm, is that a ctor?
It is defined... -
09:54 CoCoA-5 Design #1519 (New): Interpreter fn Value::from can use std::move?
- Investigate whether the template fn @Value::from@ (see @Interpreter.H@ around lines 1422--1442) can avoid copying by ...
-
10:07 CoCoA-5 Design #1520: Replace BOOST_FOREACH by new C++14 range for syntax
- Low priority because the current code works (but I would like to reduce dependency on BOOST).
This is likely to be... -
10:04 CoCoA-5 Design #1520 (Closed): Replace BOOST_FOREACH by new C++14 range for syntax
- The CoCoA-5 interpreter uses @BOOST_FOREACH@ in several places; I think the C++14 "range" @for@ syntax is essentially...
Also available in: Atom