Activity

From 06 Nov 2020 to 05 Dec 2020

14:15 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... John Abbott
14:02 Design #1529 (Feedback): INPUT questions: I have cleaned the code. All tests pass. Checking in.
John Abbott
13:55 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... John Abbott

23:19 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*
... John Abbott
11:29 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... John Abbott

20:30 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... John Abbott
11:48 Bug #1542: gfan does not "deinitialize": Now I wonder whether I disabled the call to @deinitialize@ myself.
The problem almost certainly arises only when @... John Abbott
20:28 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... John Abbott

20:49 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.
... John Abbott

16:29 Design #1391: RingElems: syntax with [ and ] ?: My copy works ok, but I must devise tests.
John Abbott

22:53 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... John Abbott

18:29 Design #1391: RingElems: syntax with [ and ] ?: The C++ version does not work: @WhatsNext@ causes too much trouble :-(
Groan... John Abbott
14:36 Design #1391: RingElems: syntax with [ and ] ?: Remove the CoCoA-5 and make it call the cocoalib version.
John Abbott
15:20 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... John Abbott
15:04 Design #1538: RingElem from string (ReadExpr): Similar problem for *@RingElem(QQ, "2*-3");@*
John Abbott
14:59 Design #1538 (Closed): RingElem from string (ReadExpr): What should the following do... John Abbott

14:11 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... John Abbott

21:13 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... John Abbott
21:02 Bug #1233: factor SEGV -- too large characteristic: Revised example (now that we're mostly 64 bit)... John Abbott

14:24 Feature #1532: Convenient RingHom pseudo-ctors: Florian mentions that Singular has something called *@imap@*...
John Abbott
14:07 Feature #1532 (In Progress): Convenient RingHom pseudo-ctors: Here is a prototype in CoCoA-5... we would also need a version for cocoalib!!... John Abbott
13:20 Feature #1532: Convenient RingHom pseudo-ctors: Here is the example Florian wanted:... John Abbott
13:14 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... John Abbott

Also available in: Atom

CoCoA » CoCoALib