Activity
From 05 Sep 2018 to 04 Oct 2018
04 Oct 2018
-
09:01 CoCoA-5 Slug #1228: SLUG: filling an array
- My proposal in comment 11 is *bad* because, for instance, the computation of an index may be lengthy or may have side...
03 Oct 2018
-
15:03 CoCoA-5 Slug #1228: SLUG: filling an array
- John Abbott wrote:
> I would hope that checking writability is cheap...
We will make some checks.
I want to desi... -
14:43 CoCoA-5 Slug #1228: SLUG: filling an array
- Here is an alternative to my comment about the semantics of assignment (in comment 7):
# check that @LHS@ is writabl... -
14:27 CoCoA-5 Slug #1228: SLUG: filling an array
- Yes, we cannot (and probably should not) stop the user from "shooting himself in the foot".
But CoCoA-5 should never...
02 Oct 2018
-
19:43 CoCoA-5 Slug #1228: SLUG: filling an array
- John Abbott wrote:
> I am inclined to think that a user who writes an assignment @LHS := RHS;@ where evaluating @RHS... -
17:05 CoCoA-5 Slug #1228: SLUG: filling an array
- A potential disadvantage of my proposed semantics is that if the RHS is expensive to evaluate, and the LHS is "obviou...
-
16:51 CoCoA-5 Slug #1228: SLUG: filling an array
- Now I fear there may be some "strange" situations in which nasty things may occur:...
-
15:46 CoCoA-5 Slug #1228: SLUG: filling an array
- I have changed @IndexedAccess::assignmentNeedsOwnership@ so that it gives @false@.
The loop is much faster (0.001s a... -
15:26 CoCoA-5 Slug #1228: SLUG: filling an array
- In @Interpreter.C@ around line 2065 there is:...
-
15:20 CoCoA-5 Slug #1228: SLUG: filling an array
- I have used profiling to confirm that the list is indeed copied (but why???)
The test code is:...
01 Oct 2018
-
11:16 CoCoA-5 Slug #1228 (In Progress): SLUG: filling an array
- I have just tried the third loop again, but after making the list @sieve@ twice as long, and the loop takes almost tw...
30 Sep 2018
-
10:11 CoCoA-5 Slug #1228: SLUG: filling an array
- I forgot to mention that @N := 9699690@ (product of all primes up to 20).
The third loop is *APPALLINGLY SLOW*, *... -
10:08 CoCoA-5 Slug #1228 (In Progress): SLUG: filling an array
- It seems that assigning to an array element is surprisingly slow.
Look at the timings in the following session:
<...
29 Sep 2018
-
12:51 CoCoALib Design #1223 (Resolved): NewPolyRing default indet names
- Removed the doc. Moved the old fns into obsolescent.
28 Sep 2018
-
20:36 CoCoALib Design #1223: NewPolyRing default indet names
- Just to remember.
This should go into obsolescent. -
18:05 CoCoALib Design #1223: NewPolyRing default indet names
- I have updated the code: sources, tests and examples.
Everything compiles, and the tests pass (after changing some e... -
14:57 CoCoALib Design #1223: NewPolyRing default indet names
- John Abbott wrote:
> Do you prefer *(A)* or *(B)* ? Opinions?
I prefer A, as I had already explained.
-
14:51 CoCoALib Design #1223: NewPolyRing default indet names
- I see two possible actions:
*(A)* remove completely the pseudo-ctor which accepts just the number of indets; the cal...
21 Sep 2018
-
16:17 CoCoALib Feature #1227: exgcd; solve Bezout equation
- Maybe restricting the problem to just 2 args is too limiting?
Consider the following 3 multivariate polynomials: @...
19 Sep 2018
-
14:23 CoCoALib Feature #1227: exgcd; solve Bezout equation
- According to Wikipedia there are Bezout domains which are not PIDs (but it seems all such non PIDs are "funny rings" ...
-
14:13 CoCoALib Feature #1227 (New): exgcd; solve Bezout equation
- I'd like to use an *@exgcd@* function: one which calculates both the GCD and the corresponding linear combination of ...
10 Sep 2018
-
12:11 CoCoA-5 Bug #1226: ExternalLibs return empty list
- fixed
(using new output of VersionInfo)
09 Sep 2018
-
13:56 CoCoA-5 Bug #1226 (Closed): ExternalLibs return empty list
- In my personal working version of CoCoA-5.2.5 the command @ExternalLibs()@ returns an empty list even though @Version...
06 Sep 2018
-
16:17 CoCoALib Design #1225: Move to C++14 (skipping C++11)
- Here is a list of "upgrades" to make to our source:
* make appropriate changes so that *@std::move@* can be used
* ... -
16:10 CoCoALib Design #1225: Move to C++14 (skipping C++11)
- Maintaining backward compatibility with pre-2011 C++ is probably fairly pointless, and is causing problems with users...
-
16:07 CoCoALib Design #1225 (In Progress): Move to C++14 (skipping C++11)
- Revise the source to use C++14 (and avoid "deprecated" features).
Also available in: Atom