Activity

John Abbott's activity

From 20 May 2021 to 18 Jun 2021

16:30 CoCoALib Bug #1601: Compilation ambiguity: I am not sure what the problem here is. @clang@ on Anna's computer seems not to have trouble.
My linux box has gcc ... John Abbott
16:28 CoCoALib Bug #1601 (Closed): Compilation ambiguity: I have looked better at Florian's problem (in issue #1600).
The cause of the trouble is that the compiler prefers to... John Abbott

16:24 CoCoALib Bug #1600: Detect updated versions of external libs: Some ideas and comments (for checks to make whenever trying to compile):
* first idea: check whether some extlib hea... John Abbott
16:19 CoCoALib Bug #1600 (In Progress): Detect updated versions of external libs: Florian Walsh reported a compilation failure after updating BOOST on his (linux) system.
My understanding is that he... John Abbott

15:04 CoCoA-5 Feature #1599 (In Progress): ConcatStr: I already have an impl (see #1587#note-6 and #1431#note-9).
I think it could be useful. The only doubt I have c... John Abbott
14:57 CoCoA-5 Feature #1599 (Closed): ConcatStr: Do we want to have a function @ConcatStr@ (and possibly a variant which puts a "separator" between the strings in the... John Abbott
14:46 CoCoALib Design #1576: cmp for machine integers: There is a (hard-to-read) description of the C++ rules for overload resolution at @https://en.cppreference.com/w/cpp/... John Abbott
14:21 CoCoALib Design #1576: cmp for machine integers: Not sure what to do.
Activating the template fn with name *@cmp@* causes overload resolution problems (seemingly eve... John Abbott

21:38 CoCoALib Design #1576: cmp for machine integers: Calling the template fn @cmp@ causes plenty of "fun" compilation problems. Not sure what to do.
The simplest is to... John Abbott
21:37 CoCoA-5 Bug #1595: Bad input causes crash: JAA now thinks that explicitly throwing an exception is probably neater than calling @reportError@.
I'll revise the ... John Abbott
15:35 CoCoA-5 Feature #1246: Revive old CoCoA4 package called "cocoa5.cpkg": I now have a version of @OperationCommunication.cpkg5@ which works for some simple examples.
Bernhard is working to ... John Abbott

15:37 CoCoA-5 Slug #31: theValue makes copy: Correcting earlier mistake (when I forgot to reload the page) John Abbott

20:42 CoCoA-5 Feature #1112: New function: IsEmpty: Is this in some way related to issue #31?
If not, delete the link I have just created above.
John Abbott
20:40 CoCoA-5 Slug #96: sort is too slow: I have just re-run the test: it took about 9.0s on my current linux laptop.
Still too slow :-(
John Abbott
20:35 CoCoA-5 Slug #31: theValue makes copy: Current plan of action:
* Anna will check in her changes (hinted at above)
* Anna will make an interim release of t... John Abbott
15:31 CoCoA-5 Slug #687 (Closed): Builtin fn makes unnecessary copy of arg: Now it takes 0.001s. No idea why it is fast now and not before.
Closing.
John Abbott

22:31 CoCoA-5 Bug #1595: Bad input causes crash: I have just tried a slightly modified test, namely... John Abbott
14:28 CoCoA-5 Bug #1595: Bad input causes crash: How should the error be reported?
In the fn @Parser::checkThereIsntAnotherUnaryPlusOrMinus@ the error is reported ... John Abbott
11:41 CoCoA-5 Slug #1597 (In Progress): GetRow/GetRows are extraordinarily slow: The problem is that *each call* to @GetRow@ makes a copy of the complete matrix!
The copy is triggered by @CoCoA::In... John Abbott
10:55 CoCoA-5 Slug #1597 (Closed): GetRow/GetRows are extraordinarily slow: For larger matrices @GetRow@ and @GetRows@ are unexpectedly slow:... John Abbott
10:50 CoCoA-5 Design #1041: Separators for elements of a list: I am not so sure about it being useful to allow a user to change the string.
However, it would be a good idea to hav... John Abbott

17:04 CoCoA-5 Bug #1594 (Feedback): Parser bug: missing close square bracket: John Abbott
16:47 CoCoALib Feature #1466: Ops += *= etc for Matrices?: Maybe we could get some benefit from using @swap@ or @std::move@?
Investigate?
John Abbott

17:02 CoCoA-5 Bug #1595: Bad input causes crash: I have not found the real bug, but do have a workaround.
I have changed *@Parser::checkThereIsntAnotherUnaryPlusOr... John Abbott

Also available in: Atom