Activity
From 08 Mar 2015 to 06 Apr 2015
02 Apr 2015
- 17:55 Support #677 (New): Credits to CoCoA-5 contributors
- If we want (and we want) to attract contributions we need to find a proper way to give them credits for their work, a...
13 Mar 2015
- 14:50 Feature #674: Ring constructor: allow empty range for indices?
- John Abbott wrote:
> I understand your point.
> Actually, I suppose the correct solution is to use anonymous ind... - 14:35 Feature #674 (In Progress): Ring constructor: allow empty range for indices?
- I understand your point. Actually, I suppose the correct solution is to use anonymous indets for the dummies, but we...
- 13:56 Feature #674: Ring constructor: allow empty range for indices?
- John Abbott wrote:
> There would be no technical problem allowing a range such as 1..0; perhaps the main question is... - 13:21 Feature #674: Ring constructor: allow empty range for indices?
- There would be no technical problem allowing a range such as 1..0; perhaps the main question is whether the gain in e...
- 11:08 Feature #674 (Rejected): Ring constructor: allow empty range for indices?
- I am writing a CoCoA-5 program which may need some "dummy" variables. My code looks like this:...
- 13:55 Support #654 (Feedback): Rename adjoint to adjugate???
- After speaking to Anna about it on Skype, we decided that it is simplest to call the function @adj@ (in the same way ...
11 Mar 2015
- 13:14 Feature #673: Error message: I was expecting...
- The relevant source code is @Parser.H:156@
The following rule may help identify the "type" of a parser token:
* s... - 13:10 Feature #673 (Closed): Error message: I was expecting...
- The generic error message...
- 13:07 Design #668: Remove keyword "weights"?
- It works... more or less. @A["weights"]@ gives the error I wanted, but @A.weights@ still gives a less helpful error....
10 Mar 2015
- 21:09 Design #668: Remove keyword "weights"?
- At the moment I have implemented @setField@ and @setFieldNoCheck@; the latter is just the old fn renamed. The new fn...
- 20:13 Design #668: Remove keyword "weights"?
- In @Interpreter.H:718@ the mem fn @setField@ is declared as @virtual@; why??
- 16:27 Bug #670: Error column indicator misaligned with non-printing (unprintable) characters
- Relevant source code is @Lexer.C:615@ and following lines.
Already have a prototype; currently prints out # instea... - 11:38 Bug #672: Emacs UI: strange string literal causes crash
- The EmacsUI really seems to do strange things when the input contains unprintable chars. I am guessing that it is th...
09 Mar 2015
- 00:45 Bug #672: Emacs UI: strange string literal causes crash
- Other chars which give trouble include those with ASCII code 3, ...
[to be completed]
- 21:35 Bug #672 (Closed): Emacs UI: strange string literal causes crash
- I created a file (@CRASH.cocoa5@) containing the following:...
- 13:49 Bug #671 (New): Emacs UI: swapped splitting
- In some cases emacs splits (top+bottom) swapping the buffers, i.e. *cocoa5* at the bottom.
Investigate and fix. - 13:33 Bug #670 (In Progress): Error column indicator misaligned with non-printing (unprintable) characters
- I was thinking that the substitution for unprintable chars would occur only when printing out source code for the pur...
- 11:26 Bug #670: Error column indicator misaligned with non-printing (unprintable) characters
- John Abbott wrote:
> A very simple idea would be to replace unprintable characters by a single printable character (...
Also available in: Atom