Activity
From 21 Oct 2020 to 19 Nov 2020
17 Nov 2020
-
22:33 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 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 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 Bug #1537: EmacUI: strange colours, sometimes
- Here is some doc about emacs;...
-
20:02 Bug #1537: EmacUI: strange colours, sometimes
- Around line 335 in @cocoa5.el@ there is this...
-
19:48 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 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 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 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 Design #1540 (Closed): Double power
- What do you think CoCoA does with the following input?...
-
09:43 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
-
16:00 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 Design #1530: VersionInfo -- better field names?
- and add Boost into the ExternalLibs record
-
15:48 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 Support #1534: Install CoCoA-5 on MacOS-10.15+
- I have had trouble installing CoCoA-5 from our website on my old mac.
-
14:48 Bug #1537 (Closed): EmacUI: strange colours, sometimes
- ...
-
11:23 Feature #1536: Implement xel?
- The matter was raised by Bernhard Andraschko. His argument is below:...
-
11:19 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 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 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 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 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 Feature #1535 (In Progress): New functions: argmin, argmax
- Here is a first prototype in CoCoA-5...
-
11:14 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 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:07 Bug #1531 (Feedback): CRASH: arithmetic with HilbertSeries (tagged object)
-
13:58 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...
06 Nov 2020
-
13:56 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 Design #1533 (In Progress): RingElem and IndetSymbols not compatible
-
13:34 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 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 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 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 Bug #1531 (Closed): CRASH: arithmetic with HilbertSeries (tagged object)
- The following input causes an assertion failure, followed by abort:...
04 Nov 2020
-
12:30 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 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 Feature #250: CoCoALib BuildInfo vs CoCoA-5 VersionInfo
- Is this issue still relevant?
Close? Reject? -
12:06 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 Bug #1527 (Feedback): Inadequate error message on incorrect list access
- I have checked in the code.
03 Nov 2020
-
22:19 Feature #1293: Vim Plugin for CoCoA
- Can we make the link for the imminent (interim) release?
-
22:17 Bug #1527: Inadequate error message on incorrect list access
- This is what happens now:...
-
21:12 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 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 Support #1459 (Closed): Manual entries for mod and div
02 Nov 2020
-
22:20 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 Bug #1527: Inadequate error message on incorrect list access
- Na toll:...
-
21:45 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 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...
30 Oct 2020
-
20:49 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 Feature #1509: RingElems with empty input
- Checked in.
-
19:58 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 Design #1525: CoCoA Manual: homogenize obsolete/obsolescent entries
- Possibly add the year
-
12:02 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 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...
29 Oct 2020
-
22:03 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 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... -
18:18 Design #1525 (In Progress): CoCoA Manual: homogenize obsolete/obsolescent entries
- Done up to letter P
-
17:50 Design #1525: CoCoA Manual: homogenize obsolete/obsolescent entries
- This is how the renamed ones should look like...
-
17:04 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 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 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... -
13:49 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 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...
28 Oct 2020
-
23:12 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 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:11 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 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 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 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 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 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 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... -
17:59 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...
26 Oct 2020
-
19:39 Feature #1509 (Resolved): RingElems with empty input
- I have improved (??) the code. It should give better err mesgs now. Here are some examples:...
-
12:08 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 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 ... -
11:49 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:15 Design #1508: Initial ring
- Presumably the CoCoA-5 interpreter has a function which performs the command *@source@*. If this function can accept...
-
10:10 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 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 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 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...
23 Oct 2020
-
20:48 Bug #1514: Cocoa crashes when calling RingElems
- MemPool causes a SEGV! 8-O
I'll try without MemPool... if I can remember how.
*ANS:* configure with @--thread... -
15:56 Bug #1514: Cocoa crashes when calling RingElems
- I have just made a first run with debugger/profiler --> SEGV
Ooops!
-
12:19 Bug #1514: Cocoa crashes when calling RingElems
- I have modified the test program so that it first generates a list of random linear forms (and then prints it).
Wi... -
10:10 Bug #1514 (In Progress): Cocoa crashes when calling RingElems
- I have just recompiled CoCoALib to use @unsigned char@ as exponent type.
The program ran noticeably faster: about 3 ... -
09:22 Bug #1514: Cocoa crashes when calling RingElems
- The test example as in the description took about 7 mins to generate the 20Mbyte file. That is disappointingly slow ...
-
16:08 Design #1508: Initial ring
- I like Anna's suggestions:
* by default start with the initial ring @QQ[x,y,z]@ (why should it be assigned to a var... -
10:00 Design #1508: Initial ring
- I vote for *(A)* Right after the banner print a message saying what the current ring is
Cleanliness would demand h... -
10:23 Feature #1516: substring function
- This ought to be very easy: I am sure that C++ already has such a function.
I came across the problem while lookin... -
10:21 Feature #1516 (Closed): substring function
- Proposal: a new function to extract a substring.
Syntax would be something like @substr(str, start, end)@ where ind... -
09:59 Feature #1509: RingElems with empty input
- Ah, me too. I have just checked in my code... oddly, there were no clashes. What does that mean?
-
09:33 Feature #1509: RingElems with empty input
- Fixed in @RingElemInput.C@, therefore also for CoCoALib.
22 Oct 2020
-
17:17 Design #635: Automatic mapping of RingElem (in operation with a compound value)
- Clarification: the example in comment 1 does indeed run, but the resulting matrix is over @P@ not @K@.
To obtain a m... -
17:10 Feature #1461: Automatic mapping for multiplication?
- I suggest closing this issue, and copying any unresolved parts into issue #7.
It would be nice to have issue #7 as t... -
17:08 Design #637: Undesirable consequence of automatic mapping of RingElems?
- I now suggest that we make equality-test throw an error (@MixedRings@) if the args are elements of two different ring...
-
16:42 Bug #1514 (Closed): Cocoa crashes when calling RingElems
- Hi,
I have a large polynomial system that has to be read from a file. In order to do so, I load all the polys as c...
21 Oct 2020
-
13:56 Feature #1509 (In Progress): RingElems with empty input
- We could add the following at the start of @RingElems@ (in @RingElemInput:C:278@)...
Also available in: Atom