Activity
From 08 Nov 2020 to 07 Dec 2020
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
-
- I downloaded gfan (v. 0.6.2) from the official website.
The subtree layout is quite different from what I have!
Als... -
- I have cleaned the code. All tests pass. Checking in.
-
- 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
-
- 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... -
- Maybe improve impl of @CoeffOfTermSparse@ in @CoCoALibSupplement.C@ around line 151?
See commented out "improved" ... -
- 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.
-
- Main.C L279
-
- This is for running CoCoAInterpreter in terminal, when it is saved in the bin/ directory.
This happens (at least) ... -
- Now CoCoAInterpreter look for packages (if not specified) in its own directory. Add also the path "../"
-
- I've done it for *@defaultPackageDir@* which is now *@IsDefaultPackageDir@*.
I find it easier, and that's the reason... -
- Should we (slowly?) adapt parser/interpreter/main to our coding conventions?
03 Dec 2020
-
- I now have a personal CoCoA version with the new @MemPool@ code (see issue #1522 comment 10).
I have just tried the ... -
- I have uncommented the suspicious commented out call in GFAN, and everything seems to work fine now.
I hope Anna c... -
- Now I wonder whether I disabled the call to @deinitialize@ myself.
The problem almost certainly arises only when @... -
- I have made a first design improvement:
There is now *@MaxSliceSize@* (in bytes); if the requested slice size is gre...
02 Dec 2020
-
- I have been "playing" with @MemPool@, and found that gfanlib seems to allocate 7 GMP values which are never freed.
...
01 Dec 2020
-
- If we choose to extend CoCoA-5, there are 2 obvious approaches:
* modify @foreach@ so that it uses references --- ob... -
- Julian Danner asks whether it would be possible to have a version of @foreach@ which operates on a reference to the l...
-
- I am tempted to remove the example of using @indent@ with 2 args: it occupies a lot of vertical space, but conveys li...
-
- Maybe this should be a new issue? I was surprised at what @indent@ did when given a module:...
26 Nov 2020
-
- I must check what happens for old MacOS
-
- My copy works ok, but I must devise tests.
-
- John Abbott wrote:
> A possible way to address the problem is to discourage users from typing *@/-@* by making it is... -
- Anna will impl in CoCoAlib, and then make accessible to CoCoA-5.
-
- 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...
-
- Very good reasoning.
Indeed some researchers have opposite standards, calling lex (and degrevlex) what we call xel (... -
- I like the idea. We need another mane for the funzion with indices.
23 Nov 2020
-
- I have checked in my changes. Let's hope everything works fine!
20 Nov 2020
-
- We still need to see where the new the @for@ syntax can be used in cocoalib -- that is issue #1346.
Maybe I should... -
- 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... -
- I would like to maintain reasonable compatibility between the way CoCoA-5 parses expressions and the way @RingElem@ o...
-
- Apparently the ability to suppress prompts could be useful for the ApCoCoA interface.
For that application, it wou... -
-
- fixed
-
- What was nice was that Bernhard wrote "shouldn't cocoa-5.2 be cocoa-5.2?"
So even bug reporters can make typos ;-)
-
- Done.
I added "Boost" only in BuiltinFunctions.C.
I have also the code for adding it in ExternalLibs.C (commented o...
17 Nov 2020
-
- The input functions are quite messy: not really a coherent design philosophy.
It seems that *@ReadExpr@* gives err... -
- Last week a student came with some problems with making CoCoA work on her MacBook; most of these are dealt with elsew...
-
- A possible way to address the problem is to discourage users from typing *@/-@* by making it issue a warning.
As a... -
- This is probably not solvable :-(
I changed the emacs syntax declaration for "minus" into just a plain "." (punctu... -
- Here is some doc about emacs;...
-
- Around line 335 in @cocoa5.el@ there is this...
-
- As far as I can tell the following "digraphs" are recognized as starting a comment:
slash-star, slash-slash, slash-m... -
- I have tried a few tests. slash-minus seems to be recognised as a comment start; I have tried slash-char where char w...
-
- 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
-
- I think CoCoA should give a warning or even an error. Currently, it gives neither!
On my computer I got *@x^8@*
... -
- What do you think CoCoA does with the following input?...
-
- The installation instructions for Microsoft refer to the directory *@C:\cocoa-5.2\emacs@* instead of *@C:\cocoa-5.3\e...
13 Nov 2020
-
- The C++ version does not work: @WhatsNext@ causes too much trouble :-(
Groan... -
- Remove the CoCoA-5 and make it call the cocoalib version.
-
- *Anna will do the following*
(1) move the info about BOOST into the subrecord @ExternalLibs@ (_i.e._ added to the li... -
- and add Boost into the ExternalLibs record
-
- Anna could you do the following on your old MacBook:
(1) download the official distrib
(2) follow the instructions ... -
- I have had trouble installing CoCoA-5 from our website on my old mac.
-
- 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...
-
- Similar problem for *@RingElem(QQ, "2*-3");@*
-
- What should the following do...
-
- ...
-
- The matter was raised by Bernhard Andraschko. His argument is below:...
-
- 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
-
- 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
-
- I clearly prefer @argmin@, since its easier to type and lower-case is also more common in mathematics, but (as for ma...
-
- What should the names be?
In most contexts they are written @argmin@ (or maybe @arg min@ with a space).
Should be u... -
- Should this actually be in CoCoALib?
Might it be handy to have a version which returns the index (or indices) of t... -
- Here is a first prototype in CoCoA-5...
-
- Proposal:
create new functions @argmin@ and @argmax@ which operate on lists.
The idea is that they return an/all ...
10 Nov 2020
-
- Review the instructions for installing CoCoA-5.3 on MacOS.
Unfortunately it seems that an administrator account an... -
- It might be possible to extend the impl give above to handle quotients of poly rings, and perhaps also "towers" of po...
-
-
- I suggest for the "Num bits" fields to the names *@NumBits_MachineInt@*, *@NumBits_MachineLong@* and *@NumBits_Small...
09 Nov 2020
-
- It is not clear to me how to implement @+=@ etc. better than the naive way, and maintain exception safety.
It migh... -
- Revised example (now that we're mostly 64 bit)...
Also available in: Atom