Activity
From 27 May 2020 to 25 Jun 2020
25 Jun 2020
-
09:51 CoCoALib Feature #1470: Get indexed indets from a polyring
- As usual, indexes should be of type @long@ (no need for @BigInt@).
It seems reasonable to allow a "short-cut" for ... -
09:48 CoCoALib Feature #1470 (New): Get indexed indets from a polyring
- Make a class so that indexed indets from a polyring can be used with their "natural" indexes (rather than, say, c++ v...
-
05:54 CoCoA-5 Feature #1469: Get indexed indets from a polyring
- There should probably be a similar fn available in CoCoALib; this implies that we'll need a type for @INTMAP@.
-
05:53 CoCoA-5 Feature #1469: Get indexed indets from a polyring
- Note that CoCoA-5 already has the (undocumented?!?) type @INTMAP@ which does exactly what we want.
Just need to ma... -
05:45 CoCoA-5 Feature #1469 (New): Get indexed indets from a polyring
- The @using@ feature of CoCoA-4 has been removed in CoCoA-5. This can cause awkwardness when the ring to be used cont...
-
05:33 CoCoALib Feature #1468: Adjoin indets to a poly ring
- Description above is incomplete:
* what term ord on @QQ[x,y,a,b]@? For impl, it would be nice if the orderings were... -
05:25 CoCoALib Feature #1468 (In Progress): Adjoin indets to a poly ring
- Make it easy to "adjoin" indets to a poly ring.
JAA thinks this means: given polyring @QQ[x,y]@ and new indets @a,...
22 Jun 2020
-
17:59 CoCoA-5 Feature #1461: Automatic mapping for multiplication?
- Here are some more places where *@ERR::MixedRings@* appears in the source -- which of these should be changed?
* *@D... -
10:54 CoCoALib Design #1467 (In Progress): Change syntax apply(phi,M) into phi(M)?
- We could permit both syntaxes, perhaps making *@apply(...)@* obsolescent?
[JAA does not much like having two differe... -
10:44 CoCoALib Design #1467: Change syntax apply(phi,M) into phi(M)?
- I noticed this while making a prototype impl for automatic ringelem promotion. In particular for ringelem times matr...
-
10:39 CoCoALib Design #1467 (Closed): Change syntax apply(phi,M) into phi(M)?
- Currently to apply a RingHom to the entries of a matrix or a C++ vector we must use the fn *@apply@*.
Is it better... -
10:34 CoCoALib Feature #1150: New fn: transform ideal with ring hom
- What is this supposed to mean? Does it mean the ideal generated by @{phi(f) | f in I}@? What else could it mean?
W... -
10:26 CoCoALib Feature #1466 (In Progress): Ops += *= etc for Matrices?
- It is not _necessary_ to make these operators, but anyone used to C++ might expect them to work.
I suggest:
* mak...
21 Jun 2020
-
11:11 CoCoALib Feature #1466 (Closed): Ops += *= etc for Matrices?
- Should we make "assign-op" operators for matrices?
20 Jun 2020
-
21:42 CoCoALib Design #1465 (In Progress): mul(MAT,MAT,MAT)
- I have commented out the fn, and modified *@power(MAT,n)@*.
Everything compiles and runs fine.
I suggest eliminat... -
21:40 CoCoALib Design #1465 (In Progress): mul(MAT,MAT,MAT)
- There is a fn *@mul(MAT,MAT,MAT)@*
Is it any use?
The impl is exception-safe, so internally it creates a new mat,... -
21:36 CoCoA-5 Feature #1461 (Resolved): Automatic mapping for multiplication?
- I have revised Anna's impl (from a joint design over the phone).
In fact we now have the four arith ops with auto ... -
21:33 CoCoA-5 Feature #7: Automatic mapping between (some) rings
- I have partly implemented this (in CoCoALib) after discussions wirh Anna (who is uncertain about some aspects).
-
21:32 CoCoA-5 Design #635: Automatic mapping of RingElem (in operation with a compound value)
- The example in comment 1 works with my current "internal" versions of CoCoA5.
19 Jun 2020
-
20:27 CoCoALib Design #1462: Change CoCoA_ERROR into CoCoA_THROW_ERROR
- I have removed the macro *@CoCoA_THROW@* for the following reasons:
* a macro is an ugly implementation trick
* it ... -
09:41 CoCoALib Design #1464 (New): What is the difference between InterruptReceived and InterruptedBySignal
- It seems to be superfluous to have both *@InterruptReceived@* and *@InterruptedBySignal@*.
Review the design/impl; a...
17 Jun 2020
-
21:02 CoCoALib Design #1462 (Feedback): Change CoCoA_ERROR into CoCoA_THROW_ERROR
- I have updated doc too. Also checked that everything works with debugging active.
-
20:08 CoCoALib Design #1462: Change CoCoA_ERROR into CoCoA_THROW_ERROR
- I have changed all calls to @CoCoA_ERROR@ into @CoCoA_THROW_ERROR@; I do think the code is a bit more readable with @...
-
20:19 CoCoALib Design #1463 (In Progress): SmoothFactor: use FactorMultiplicity
- The current implementation of @FactorMultiplicity@ makes it hard to use inside @SmoothFactor@ (because it returns onl...
16 Jun 2020
-
20:03 CoCoALib Design #1462 (In Progress): Change CoCoA_ERROR into CoCoA_THROW_ERROR
- I have started. Defined the new macros @CoCoA_THROW_ERROR@ (drop in replacement for current @CoCoA_ERROR@).
Also de... -
16:55 CoCoALib Design #1462 (Closed): Change CoCoA_ERROR into CoCoA_THROW_ERROR
- I suggest changing name of the macro to *@CoCoA_THROW_ERROR@* so that it i obvious to the reader that the error objec...
-
20:01 CoCoALib Feature #1457 (Feedback): Make SmoothFactor interruptible
- Speed test was OK. Also improved impl of @SmoothFactor@, but see #1463.
Checked in.
-
16:29 CoCoALib Feature #1457 (Resolved): Make SmoothFactor interruptible
- The problem is that @SmoothFactor@ has two (nested) loops either of which can be slow; but I had inserted a call to @...
-
19:56 CoCoALib Design #1463 (Closed): SmoothFactor: use FactorMultiplicity
- @SmoothFactor@ contains almost a duplicate implementation of @FactorMultiplicity@.
Tidy up: Make @SmoothFactor@ ca... -
19:54 CoCoALib Slug #1170: SmoothFactor: slow when a factor is found
- The given example is no longer slow.
The trick of testing for primality is used only when @RemainingFactor@ is not t... -
16:50 CoCoA-5 Bug #1412: Emacs UI: font size
- See also @https://stackoverflow.com/questions/2238418/emacs-lisp-how-to-get-buffer-major-mode@
Emacs BUG: It seems... -
16:45 CoCoALib Bug #1458 (Rejected): Redesign interrupt mechanism?
- What I wrote in comment 5 was perhaps once correct, but not any longer.
This bug did not exist where I thought it ex...
10 Jun 2020
-
16:20 CoCoA-5 Feature #1461: Automatic mapping for multiplication?
- use try/catch for better error message?
direct use of myMulByCoeff for efficiency? Is it worth it? (John guesses not) -
16:17 CoCoA-5 Feature #1461: Automatic mapping for multiplication?
- Talking with John, getting bored in the hospital ;-)
first implementation
-
16:06 CoCoA-5 Feature #1461 (Closed): Automatic mapping for multiplication?
Also available in: Atom