Activity
From 14 Nov 2020 to 13 Dec 2020
13 Dec 2020
-
17:16 CoCoA-5 Bug #1552: subst: not checking args properly
- @subst@ is defined in package @misc@.
The real problem appears to be in @Subst2_top@:
@x+2@ is evaluated in @ZZ/(... -
17:13 CoCoA-5 Bug #1552 (New): subst: not checking args properly
- The following shows that @subst@ can behave wrongly:...
-
11:07 CoCoA-5 Design #1551: Emacs: avoid making buffer visible in 2 "windows"?
- After a quick search I found the following useful link:
*@https://emacs.stackexchange.com/questions/2959/how-to-kn... -
11:06 CoCoA-5 Design #1551 (New): Emacs: avoid making buffer visible in 2 "windows"?
- In Emacs if I type @M-x cocoa5 RET@ it changes the current "window"(?) to show @*cocoa5*@ buffer even if this buffer ...
12 Dec 2020
-
21:37 CoCoA-5 Design #1550 (Feedback): version number for CoCoA5 snapshot release?
- I have checked in: better doc in @release-files/version@, new target in @Makefile@, new program @check-version-define...
-
21:36 CoCoA-5 Bug #1512 (Feedback): Package with unexpected EOF
- I have checked the code in. No test (do we need one?)
11 Dec 2020
-
21:54 CoCoA-5 Design #1550 (Resolved): version number for CoCoA5 snapshot release?
- I have added a safety check. It seems to work well enough.
Tomorrow I'll check it in.
-
21:09 CoCoA-5 Design #1550: version number for CoCoA5 snapshot release?
- I have now checked where the values of @COCOA5_VER_MAJ@ etc are used.
I believe it is safe if they contain alphanume... -
14:31 CoCoA-5 Design #1550 (In Progress): version number for CoCoA5 snapshot release?
- I changed the file @src/CoCoA/release-files/version@ so that the 3rd component was @3b@ (instead of just @3@).
CoCoA... -
12:20 CoCoA-5 Design #1550 (Closed): version number for CoCoA5 snapshot release?
- should we have finer numbering?
such as cocoa-5.3.3b? -
14:24 CoCoA-5 Bug #1512 (Resolved): Package with unexpected EOF
- I think I have fixed it: it now produces this error report:...
-
12:30 CoCoA-5 Design #1545: CoeffOfTerm: in CoCoALibSupplement
- The code is there, currently commented out.
What we have occasion to use it and test speed in a real contest (when w... -
12:01 CoCoA-5 Design #1544: CoCoA coding conventions for parser/interprer?
- Discussion with John: OK, updating the style "as we go".
Keep *@theRing@* & co. for *@intrusive_ptr@* (at least to... -
11:55 CoCoA-5 Design #1546 (In Progress): Improve 'describe' or 'print' for a function
- If the fn comes from a package, can the name of the pkg be given (perhaps in a comment)?
-
09:38 CoCoA-5 Design #1546: Improve 'describe' or 'print' for a function
- Anna Maria Bigatti wrote:
> Maybe we could have @print/print .. on ..@ actually printing the function.
I have it ... -
11:53 CoCoA-5 Feature #1174 (In Progress): package of a function --> of an identifier!
-
11:48 CoCoA-5 Feature #1174: package of a function --> of an identifier!
- Anna has a prototype in @coclib.cpkg5@. Currently commented out -- how long has it been there??
If it were built-... -
09:41 CoCoA-5 Feature #1549 (In Progress): Add sagbi package
- I have a package ready for computing sagbi bases.
Confirm syntax and write manual.
09 Dec 2020
-
08:54 CoCoA-5 Design #1546: Improve 'describe' or 'print' for a function
- Anna Maria Bigatti wrote:
> Julian Danner wrote:
> > sadly CoCoA does not offer a (nice) way to save objects (rings... -
08:03 CoCoA-5 Design #1546: Improve 'describe' or 'print' for a function
- Julian Danner wrote:
> sadly CoCoA does not offer a (nice) way to save objects (rings, polys, lists,...) in such a w...
08 Dec 2020
-
14:29 CoCoA-5 Support #1548 (New): Man page for UniversalGBasis
- The manual page for @UniversalGBasis@ could be clearer.
Improve it!
07 Dec 2020
-
16:17 CoCoA-5 Design #1546: Improve 'describe' or 'print' for a function
- I have had a (not so) quick look at the code involved.
*@describe@* like all CoCoA commands returns no value, and th...
05 Dec 2020
-
14:15 CoCoALib Bug #1542: gfan does not "deinitialize"
- I downloaded gfan (v. 0.6.2) from the official website.
The subtree layout is quite different from what I have!
Als... -
14:02 CoCoALib Design #1529 (Feedback): INPUT questions
- I have cleaned the code. All tests pass. Checking in.
-
13:55 CoCoALib Design #1547 (Closed): Require decimal mode for ostream?
- In issue #1529 we have decided to require that when reading from an @istream@ the stream must be in decimal mode.
Sh...
04 Dec 2020
-
23:19 CoCoALib Design #1523 (Feedback): Input fns: action when when istream is in bad state?
- I have also modified and checked in @symbol.C@
*Conclusion: input fns throw if @istream@ is not in good state*
... -
12:53 CoCoA-5 Design #1546 (Closed): Improve 'describe' or 'print' for a function
- Hi,
sadly CoCoA does not offer a (nice) way to save objects (rings, polys, lists,...) in such a way that they can be... -
11:57 CoCoA-5 Design #1545 (New): CoeffOfTerm: in CoCoALibSupplement
- Maybe improve impl of @CoeffOfTermSparse@ in @CoCoALibSupplement.C@ around line 151?
See commented out "improved" ... -
11:29 CoCoALib Design #1529 (Resolved): INPUT questions
- Update:
* an exception is thrown if the @istream@ is not in "decimal" mode
* no spaces are allowed inside a rationa... -
10:26 CoCoA-5 Feature #1543 (Feedback): Default path for packages
- Done and tested. cvs-ed.
-
09:40 CoCoA-5 Feature #1543: Default path for packages
- Main.C L279
-
09:37 CoCoA-5 Feature #1543: Default path for packages
- This is for running CoCoAInterpreter in terminal, when it is saved in the bin/ directory.
This happens (at least) ... -
09:31 CoCoA-5 Feature #1543 (Closed): Default path for packages
- Now CoCoAInterpreter look for packages (if not specified) in its own directory. Add also the path "../"
-
09:51 CoCoA-5 Design #1544: CoCoA coding conventions for parser/interprer?
- I've done it for *@defaultPackageDir@* which is now *@IsDefaultPackageDir@*.
I find it easier, and that's the reason... -
09:47 CoCoA-5 Design #1544 (New): CoCoA coding conventions for parser/interprer?
- Should we (slowly?) adapt parser/interpreter/main to our coding conventions?
03 Dec 2020
-
21:31 CoCoA-5 Bug #1514 (Closed): Cocoa crashes when calling RingElems
- I now have a personal CoCoA version with the new @MemPool@ code (see issue #1522 comment 10).
I have just tried the ... -
20:30 CoCoALib Bug #1542 (In Progress): gfan does not "deinitialize"
- I have uncommented the suspicious commented out call in GFAN, and everything seems to work fine now.
I hope Anna c... -
11:48 CoCoALib Bug #1542: gfan does not "deinitialize"
- Now I wonder whether I disabled the call to @deinitialize@ myself.
The problem almost certainly arises only when @... -
20:28 CoCoALib Bug #1522: SEGV: avoid long linked lists of loaves in MemPools
- I have made a first design improvement:
There is now *@MaxSliceSize@* (in bytes); if the requested slice size is gre...
02 Dec 2020
-
20:49 CoCoALib Bug #1542 (In Progress): gfan does not "deinitialize"
- I have been "playing" with @MemPool@, and found that gfanlib seems to allocate 7 GMP values which are never freed.
...
01 Dec 2020
-
14:03 CoCoA-5 Feature #1541: foreach with ref to list entry?
- If we choose to extend CoCoA-5, there are 2 obvious approaches:
* modify @foreach@ so that it uses references --- ob... -
13:58 CoCoA-5 Feature #1541 (New): foreach with ref to list entry?
- Julian Danner asks whether it would be possible to have a version of @foreach@ which operates on a reference to the l...
-
12:13 CoCoA-5 Support #1298: How can user find the indent command?
- I am tempted to remove the example of using @indent@ with 2 args: it occupies a lot of vertical space, but conveys li...
-
12:08 CoCoA-5 Support #1298: How can user find the indent command?
- Maybe this should be a new issue? I was surprised at what @indent@ did when given a module:...
26 Nov 2020
-
16:33 CoCoA-5 Support #322: Installation instructions (on website)
- I must check what happens for old MacOS
-
16:29 CoCoALib Design #1391: RingElems: syntax with [ and ] ?
- My copy works ok, but I must devise tests.
-
16:24 CoCoA-5 Bug #1537: EmacUI: strange colours, sometimes
- John Abbott wrote:
> A possible way to address the problem is to discourage users from typing *@/-@* by making it is... -
16:20 CoCoA-5 Feature #1536: Implement xel?
- Anna will impl in CoCoAlib, and then make accessible to CoCoA-5.
-
16:06 CoCoA-5 Feature #1536: Implement xel?
- One difference between @QQ[x,y,z],xel@ and @QQ[z,y,x],lex@ is that the order in which the idents are printed is diffe...
-
14:37 CoCoA-5 Feature #1536 (In Progress): Implement xel?
- Very good reasoning.
Indeed some researchers have opposite standards, calling lex (and degrevlex) what we call xel (... -
15:52 CoCoA-5 Feature #1535: New functions: argmin, argmax
- I like the idea. We need another mane for the funzion with indices.
23 Nov 2020
-
10:18 CoCoA-5 Design #1520 (Feedback): Replace BOOST_FOREACH by new C++14 range for syntax
- I have checked in my changes. Let's hope everything works fine!
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...
Also available in: Atom