CoCoA-5: Issueshttps://cocoa.dima.unige.it/redmine/https://cocoa.dima.unige.it/redmine/redmine/favicon.ico?15088260392014-04-09T22:44:13ZCoCoA Project
Redmine Design #534 (Closed): Remove float.cpkg5https://cocoa.dima.unige.it/redmine/issues/5342014-04-09T22:44:13ZJohn Abbott
<p>All the fns which were exported by <code>float.cpkg5</code> are now in CoCoALib.</p>
<p>Remove <code>float.cpkg5</code>?</p> Design #532 (Closed): New package: OBSOLESCENThttps://cocoa.dima.unige.it/redmine/issues/5322014-04-09T15:46:00ZJohn Abbott
<p>Create a new package called <code>OBSOLESCENT.cpkg5</code> into which we put obsolescent functions (with an "expiration date").</p> Feature #529 (Closed): Naive version of resolution and Betti numbershttps://cocoa.dima.unige.it/redmine/issues/5292014-04-09T08:19:49ZAnna Maria Bigatti
<p>Implement a naive version of resolution and Betti numbers while hoping for the (very delicate) optimized <strong>resolution</strong> algorithm implementation.</p> Feature #502 (Closed): New fn/object type: timerhttps://cocoa.dima.unige.it/redmine/issues/5022014-03-30T19:58:56ZJohn Abbott
<p>Here's an idea. Create a new fn called <strong><code>timer</code></strong> (or *<code>NewTimer</code>) which creates a <code>TIMER</code> object.<br />When you evaluate the object it simply return the amount of CPU time used since it was created.</p>
<p>Thus to time a computation you could do this:<br /><pre>
T := timer();
XYZ := LongComputation();
PrintLn "Time taken: ", DecimalStr(T);
</pre></p>
<p>Is this a good idea? Is it worth it?<br />Does it give any real advantage over <code>CpuTime()</code>?</p>
<p><strong>2014-04</strong> conclusion: this solution is now implemented<br /><pre>
T := CpuTime();
-- long computation --
TimeFrom(T); -- to print it in decimal
CpuTimeFrom(T); -- to have it as a usable number (as CpuTime())
</pre></p> Design #475 (Closed): Eliminate package approxhttps://cocoa.dima.unige.it/redmine/issues/4752014-03-14T19:18:58ZJohn Abbott
<p>Implement in CoCoALib the fns in package <code>approx</code>; then eliminate the package.<br />Some fns are already in CoCoALib.</p> Design #472 (Closed): Record keywordhttps://cocoa.dima.unige.it/redmine/issues/4722014-03-13T14:07:22ZJohn Abbott
<p>What capitalization do we want for the keyword <code>Record</code>?</p>
<p>Currently CoCoA-5 uses <code>Record</code>, but the manual prefers <code>record</code>.</p>
<p>Make preferences of CoCoA and the manual coincide!</p> Bug #462 (Closed): Emacs UI: semicolon problemshttps://cocoa.dima.unige.it/redmine/issues/4622014-03-09T20:16:43ZJohn Abbott
<p>Semicolon sometimes does strange things.</p>
<p>It places the cursor in the wrong place if you type semicolon immediately after a string whose last word is a keyword:<br /><pre>
PrintLn "No solution for ";
</pre><br />Typing the above puts the cursor immediately after <code>for</code>, not after the semicolon as one would expect.</p>
<p>Something similar occurs if you try to type a semicolon in a string.</p> Bug #460 (Closed): Emacs UI: updating abbrev-tablehttps://cocoa.dima.unige.it/redmine/issues/4602014-03-09T09:04:15ZJohn Abbott
<p>I changed my <code>cocoa5.el</code> file and was surprised to find that some keywords which have now been removed were still recognized (and "expanded") by Emacs.</p>
<p>The problem seems to be that at some point I told Emacs to save its abbrevs (in file <code>$HOME/.abbrev_defs</code>), and that these abbrevs are automatically loaded (after the new <code>cocoa5-mode</code> definitions).</p>
<p>How to fix this?</p>
<p><strong>2014-04</strong> conclusion: it does not seem to be possible to avoid "some" automatic saving, but all-or-nothing. So we set it for "no-auto-save" in cocoa5.emacs (the file for "Preferences"). Anyway capitalization is no longer necessary and now can be disabled (see <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: EmacsUI: lower case keywords (Closed)" href="https://cocoa.dima.unige.it/redmine/issues/523">#523</a>)</p> Bug #441 (Closed): Emacs UI: C-c C-e does not ignore keywords inside stringshttps://cocoa.dima.unige.it/redmine/issues/4412014-02-12T11:00:56ZJohn Abbott
<p>The emacs key sequence <code>C-c C-e</code> should automatically insert the correct <code>End...</code> keyword to close a syntactical construct. It works unless a CoCoA keyword appears inside a string literal -- I quite often write strings containing the word "for".</p>
<p>Fix it (at least for normal string literals)!</p> Feature #414 (Closed): New fn to increase max recursion depthhttps://cocoa.dima.unige.it/redmine/issues/4142013-11-22T16:59:34ZJohn Abbott
<p>Add a new fn to allow the user to increase the max recursion depth (currently hardwired to 2000)</p>
<p>What should the fn do with "ridiculous" inputs?<br />What values are considered not "ridiculous"?</p> Feature #381 (Closed): Emacs User Interface: Easier binding for sending a line to cocoa-5https://cocoa.dima.unige.it/redmine/issues/3812013-06-26T14:45:50ZAnna Maria Bigatti
<p>set an easier binding (easier than C-c C-l) for sending a line to cocoa-5.<br />Macaulay-2 mode sets f11, but that's unconvenient on Macintoshes.<br />I prefer <strong>C-return</strong></p>
<p><strong>2014-04</strong> conclusion: many possibilities implemented <strong>C-RET</strong>, <strong>M-RET</strong> (also <strong>C-c RET</strong>)</p> Feature #362 (Closed): New function: IsZeroDivisorhttps://cocoa.dima.unige.it/redmine/issues/3622013-05-29T17:16:46ZAnna Maria Bigatti
<p>Implement in as many cases as possible <strong>IsZeroDivisor</strong><br />(see related issue for CoCoALib)</p> Design #301 (Closed): How to obtain an integer from a finite field element? AsINT?https://cocoa.dima.unige.it/redmine/issues/3012013-02-08T17:12:14ZJohn Abbott
<p>Let <code>X</code> be a ring elem belonging to a finite field.<br />How can I get an integer value from <code>X</code>?<br />At the moment <strong><code>AsINT(X)</code></strong> gives an error (about characteristic being non-zero); but in CoCoALib <code>IsInteger</code> succeeds.</p>
<p>What is the right way to do it?</p> Feature #200 (Closed): add modules and module operationshttps://cocoa.dima.unige.it/redmine/issues/2002012-06-29T16:53:55ZAnna Maria Bigatti
<p>We have modules in CoCoALib.<br />Just mimick ideals to add modules..... will it be that easy?</p>
<p>Probably we'll have some surprises with module operations... cross fingers!!</p> Feature #18 (Closed): Printing matrices: I/O unified style for CoCoA-5?https://cocoa.dima.unige.it/redmine/issues/182011-11-02T14:58:12ZAnna Maria Bigatti
<p>Currently matrices are printed by CoCoALib like this:<br /><pre>
matrix(QQ)(3, 3)
[
[1, 0, 0],
[0, 1, 0],
[0, 0, 1]
]
</pre><br />But this is tedious to be used as CoCoA-5 input (unless we define matrix in CoCoA-5 as a function returning a function returning ad indexable object, but this is quite unnatural)<br />Some options:<br /><pre>
matrix // QQ (3, 3)
([
[1, 0, 0],
[0, 1, 0],
[0, 0, 1]
])
</pre><br />or<br /><pre>
matrix(QQ, 3, 3,
[
[1, 0, 0],
[0, 1, 0],
[0, 0, 1]
])
</pre><br />There are also these two CoCoA-5 functions: MakeMatByRows and MakeMatByCols<br /><pre>
MakeMatByRows(2, 10, 1..20);
</pre><br />defined in packages/matrix.cpkg5. Should we unify syntax/meaning?</p>