Activity
From 26 Feb 2014 to 27 Mar 2014
27 Mar 2014
-
18:33 Bug #171: Negate LIST, MAT,...
- If @L@ is a list C5 cannot compute @-L@ but it can compute @(-1)*L@ and also @L1-L2@ if @L1@ and @L2@ are lists. Thi...
-
- *ADD* this code as a CoCoA-5 package (or reimpl in CoCoALib).
26 Mar 2014
-
17:09 Feature #365 (Feedback): add function to compute minimal generators (like Minimalize)
- Was tougher than I expected: ironically the core code (GBasis) was all done, but updating the module/submodule/FGModu...
-
- Written documentation.
The only negative aspect is that the user must write @ref@ before the arg;
if we define co...
25 Mar 2014
-
- Add an easily accessible manual page about creating lists, and perhaps simple operations on them (indexing, concatena...
-
- I have added a manual page entitled *@updating CoCoA-4 code@*; and another entitled *@CoCoA-4 mode@* (about @***...**...
-
- Placing defns of @incr@ and @decr@ in @NotBuiltin@.
JAA will add doc. -
- Delayed several issues to 5.1.0.
-
- Changed title etc to refer to 5.0.9 instead of 5.0.4.
Hoping to complete the release by the end of this week!
-
-
-
-
-
- This is going to be a pain to sort out -- delaying until 5.1.0.
Probably command line option is simplest "quick fi... -
- No trouble after 1 month in feedback.
Minor revision to the documentation.
Closing.
-
- I have left the name "lambda" in the code for lexer/parser/interpreter since anyone playing with that code should kno...
-
- Our solution should handle several cases:
*(a)* new CoCoA user with new emacs installation (_i.e._ no @.emacs@ file)
... -
- The instructions on the web site do not work because the OS refuses to run a script of unknown provenance.
How to ... -
- Still missing: function on submodules!
If we have that working than we can have a silly/slow but working version of ...
24 Mar 2014
-
- Check all functions and update the manual.
Choose the "official name" for functions. -
- John Abbott wrote:
> Note that I have also added a warning when @/*@ is found inside a @/*...*/@; this should avoid ... -
- John Abbott wrote:
> I have changed the warning level to @WS_PEDANTIC@, so most users won't see the warnings.
I thin... -
- @SetWarningLevel@ sounds good and clear!
-
- Since C5 has several "warning levels", let the (advanced) user change the level (_e.g._ in the @init.cocoa5@ file).
...
23 Mar 2014
-
- I felt better before looking at this code...
Giving up!
-
- I guess the relevant fn is @cocoa5-calculate-indent@ on line @cocoa5.el:716@
*AARRGHHH* it's almost 100 lines long !?! -
- The simplest "solution" would be to document that the emacs UI does not handle multiline comments intelligently.
A... -
- I think the current state is a fair compromise; so changing status to @feedback@
-
- I have modified the emacs fn @cocoa5-electric-semi-or-dot@.
It now calls @expand-abbrev@ only when point is in code....
22 Mar 2014
-
- The packages that "upset" me the most are @coclib@ and @primary@ (or @radical@?)
-
- There is a *HUGE* amount of cruft in the C5 packages; more than enough to make maintenance much harder than necessary...
-
- Anna could you check that this now does more or less what you want; if so, change state to feedback?
-
- I think this issue is resolved now -- any objections?
*The solution is (c)*: multiline @/*...*/@ allowed but issues ... -
- I have changed the warning level to @WS_PEDANTIC@, so most users won't see the warnings.
[now I have to change my se... -
- Well, I didn't wait for anyone else's opinion. I've implemented the warning....
-
- I suggest adding a warning if @/*@ is found inside a @/*...*/@ comment. This would alert users to a (probable?) pres...
21 Mar 2014
-
- @FactorMultiplicity@ is defined in @GCDFreebasis.cpkg5@
-
- CoCoA-5 has two virtually identical fns *@valuation@* and *@FactorMultiplicity@*.
We need only one of them!
Decid... -
- JAA will ensure that all existing packages work without @BackwardCompatible.cpkg5@; this is simply a matter of code c...
-
- added test in cocoalib. closing.
-
- ehm.... most of them yes ;-) except SparsePolyRing ideals (I think).
Looking at all of them I'm getting convinced... -
- Do the @myIntersect@ functions have assertions that their args are valid?
-
- done and added to test-ideal1.
Added the zero ideal case to... -
- I have already improved the page "Intro to Strings"; but there are several other pages which need to be merged into a...
-
- The CoCoA-5 documentation for strings needs to be tidied up, and properly integrated.
-
- It works on homogeneous input.... I would really need a volunteer to test the non-homogeneous case (either that or an...
-
- The CoCoA online manual should also have a short message on each page about functions/operators where changes are nee...
-
- Tips on updating old C4 code to C5:
* @Not@ operator now replaced by function @not@ which requires brackets!
* @LinKe... -
- We need to produce a manual page about porting old C4 code to C5.
-
- resurrected. now it needs to be filled ;-)
-
- no more problems have arisen. closing.
-
- No problems have arisen. Closing.
-
- No problems have arisen. Closing.
-
- I like defining (mathematically) matrix multiplication by scalar products, so I'm in favour of adding it.
*GetRow* w... -
- I'm rather undecided about this.
I suppose KISS would say not to widen the arg types accepted by @ScalarProduct@, ... -
- Yesterday I saw some old C4 code. In it the author had a call of the form @ScalarProduct(M[I],L)@ where @M@ is a mat...
-
- (a problem has arisen ;-)
added Not, NOT in *BackwardCompatible* -
- I implemented *GeneralMinGens* for the non-homogeneous case: it does the obvious check on every generator.
Obviously ... -
- updated manual (will not work on quotients, no need).
Still lacking: module -- is that _essentially_ trivial? (modu... -
- trivial issue, all done. Closing.
-
-
- some improvement in the download page and in the "older versions" page
20 Mar 2014
-
- How to determine the "scope" of a variable?
A function comprises a sequential succession of "top-level" commands; the... -
- The warning are sometimes is needlessly alarmist:...
-
- Let's do it as in cocoa-4: there was an init file for everyone and an additional userinit file for user preferences.
... -
- The @init.cocoa5@ file should be in a personal location (presumably home directory) and not with the files that form ...
-
- I thought that would be so easy and now I see a little problem.
CoCoA-5 loads all the files in the directory @packag... -
- I would set for @init@, same as in cocoa-4.
My personal file just contains the line @Use R;@ ;-) -
- The name *@init.cocoa5@* is reasonable; are there any other candidates?
*@StartUp.cocoa5@*
*@settings.cocoa5@*
[... -
- I agree that it is a good idea:
* beginners will find CoCoA-5 immediately usable (as CoCoA-4 was)
* advanced users ... -
- This is in fact trivial to do it: we just have to add such file to the packages directory (at it was done in CoCoA-4)...
-
- In CoCoA-4 there was a file called @init.coc@ with some "initial" settings.
Now most initialization are done by CoCo... -
- No problems for over a year --> closing!
-
- Current cvs produces a "warning". That's very good for maintainers who have to deal cleanly with lots of code.
Fo... -
- That would be handy! But I expect it to be hard to implement.
Right now the closer you can get to it is ...
19 Mar 2014
-
- We must determine the exact semantics (C4 was pretty vague, I believe).
We should decide what syntax to use.
It m... -
- Sorry, I thought I was already in CoCoA-5
-
- CoCoA-4 has the *@::@* operator which evaluated expressions in a given ring:...
-
- Conceptually this issue seems practically identical to #482.
Yet, I think they are slightly independent: if CoCoAL... -
- If a user creates the same ring twice, should he get the exact same ring?...
-
- A significant problem is that the printed form is produced by CoCoALib which naturally knows nothing about variable v...
-
- Having just recently discovered that commenting out the printed matrix with ...
-
- Here are some thoughts about @InputForm@ (or whatever it will be called):
* it could be a separate command or perhap... -
- I have just checked in the revised @getStringLiteral@ (the old one is commented out).
Multiline strings were never... -
- I have made a copy of @Lexer::getStringLiteral@ which handles only normal string literals. It is 60 lines long compa...
-
- John Abbott wrote:
> Somehow we'll have to tell those who have created @.abbrev_defs@ to remove it (or edit it to rem...
18 Mar 2014
-
- JAA thinks is would be too costly to change the Emacs code to handle this correctly (especially considering its low i...
-
- My opinion is:
(a) is too drastic: not backward compatible, single line @/*...*/@ can be useful
(b) my favourite (and... -
- Multiline comments are convenient, inconvenient and potentially hazardous.
Convenient for commenting out blocks of... -
- Our options are:
# remove all code related to multiline string literals
# comment out all code related to multiline... -
- The source code relating to the recognition of string literals is in @Lexer.C:423--511@...
-
- A purely practical point: the C5 interpreter was not designed to handle nested @/*...*/@ comments, and I'm pretty cer...
-
- I introduced the bug when "correcting" some redundant looking code (see post 1 in #441).
I've now restored the cod... -
- Somehow we'll have to tell those who have created @.abbrev_defs@ to remove it (or edit it to remove the @cocoa5-abbre...
-
- A possibly simpler solution to the problem would be to have a function *@PackageOf@* which says which package protect...
-
- Packages export their varables in the function:...
-
- The relevant source code appears to be in @Interpreter.C:229@:...
-
- No problems have arisen in 2 weeks, so I'm closing this issue.
-
- Since Anna cannot recall what the problem was, and some simple _ad hoc_ tests encountered no problems, I shall to "re...
-
- The modified impl seems OK to me.
I have modified the CoCoA-5 doc too: @Functions@ is now marked as *obsolete*;
@des... -
- I think I've corrected the code so that exported names appear first.
Will check after lunch.
-
- The relevant source code is in @Interpereter.C:233@...
-
- CoCoA-5 used more than 6Gbytes of memory while trying to compute @gcd(f,x^(31^6)-x)@ in @ZZ/(31)[x]@ where @f := x^15...
17 Mar 2014
-
- Here is why I think nested "multiline" comments are problematic; essentially the parser is compelled to parse the com...
-
- CoCoA-4 had nested comments /* /* */ */.
In CoCoA-5 G.Lagorio refused to maintain that feature because _"C does not a... -
- John Abbott wrote:
> Several packages refer to non exported functions by calling them with the prefix @$.@.
>
> Appa...
16 Mar 2014
-
- Several packages refer to non exported functions by calling them with the prefix @$.@.
Apparently this is no longe...
14 Mar 2014
-
- I have removed several uses of @Alias@ but making use of @$.@ in packages.
There are some cases where it cannot be... -
- I think the concept of @Alias@ is no longer needed (or only very rarely).
Can we eliminate it?
-
- Package @io@ does not do much currently; can we eliminate it?
-
- Implement in CoCoALib the fns in package @approx@; then eliminate the package.
Some fns are already in CoCoALib. -
- Implement in CoCoALib the fns in package @BinRepr@; some of this has already been done.
Then eliminate the package.
-
- While checking in I noticed a "valid use" for multiline comments: in the file @latex.cpkg5@ there are some examples/t...
13 Mar 2014
-
- I was wrong: it wasn't so easy to write the elisp function, but I think I have one which works now! :-)
Next step ... -
- I think it may be useful to have an emacs fn which says whether @point@ is in a string literal, in a comment, or in c...
-
- My suggestion about juxtaposition of string literals is *not backward compatible* because juxtaposition is already de...
-
- We could define juxtaposition of normal string literals to mean concatenation with a newline inserted between the two...
-
- For the same reasons I do not like multiline comments, I have grave doubts about multiline string literals. They see...
-
- Also consider @Record@ in @cocoa5-mode-abbrev-table@.
Similar questions about most CoCoA-5 keywords! -
- What capitalization do we want for the keyword @Record@?
Currently CoCoA-5 uses @Record@, but the manual prefers @... -
- I made an "older versions" page.
Now the download pages show only the latest version.
12 Mar 2014
-
- John Abbott wrote:
> A quick test suggests that this does not work, or at least not as I would like (_e.g._ @Lambda@ ... -
- John Abbott wrote:
> One post I read suggested that @cocoa5-abbrev-table@ should be @cocoa5-mode-abbrev-table@. Inv... -
- Added entry "All CoCoA Commands".
It only gives the list of entries with type "command".
Fairly easy to add (still ... -
- What I mean is just the *keywords* and syntax of CoCoA language:
* @Return@ _expr_
* @If@ _bool-expr_ @Then@ _cmd_ @E... -
- You mean something like...
-
- Yes, I mean CoCoALanguage *commands*; no, I don't mean *functions*!
Possibly a few important functions could be name... -
- John Abbott wrote:
> I have inserted the following in @Lexer.C:83@ right before the declaration of the variable @cha... -
- I have inserted the following in @Lexer.C:83@ right before the declaration of the variable @chars@ (what purpose doe...
-
- Places we should look at for changing the parser so that it warns about (or complains about) multiline comments:
@... -
- I've modified all packages so that they use either end-of-line comments (if possible) or single-line embedded comment...
-
- I've updated the CoCoAManual entry; it doesn't say that @/*...*/@ works for multiline comments (but it doesn't forbid...
-
- Here is another option:
*(C2)* In CoCoA-5.1 continue to allow the multiline syntax, but issue warnings every time a ... -
- One reason for having multiline comments is that it becomes easy to comment out blocks of code; this is also what pro...
-
- As already pointed out in #469 (update 2) I think we should aim to make multiline comments obsolescent. Here are som...
-
- C5 does not support nested multiline comments.
The following input produces @7@... -
- Here are some test cases; I use @#@ to mark the position of the cursor.
*Case 1*... -
- When there is no block to close @cocoa5-close-block@ behaves strangely.
If there is no code before @point@ then it... -
- I think this issue is unimportant because it is hard to imagine when someone would use a multiline comment to comment...
-
- I fear that it would be quite tricky to solve this one properly. Reverse scanning to decide if some line is inside a...
-
- The close block fn @C-c C-e@ gets confused by unclosed code blocks inside multiline comments. Here is an example:
<... -
- If we have a global variable, we could make it 3-state: @horizontal-split@, @vertical-split@ or @auto@.
If we do t... -
- Recall that @?@ simply has to be the first non-space character in a command (and not the first non-space character on...
-
- I have identified one case where indentation in a @cocoa5@ file goes wrong.
I have checked that @C-c C-e@ is confuse...
11 Mar 2014
-
- You mean the syntax of all commands in CoCoA?
that's not difficult, but it's going to be huge!
-
- Such a page would be useful for people who already know how to program, and simply want to see the complete syntax al...
-
- I suggest adding a page which summarises briefly the language syntax of CoCoA-5 (with link to each detailed page for ...
-
- Also remove @DegLex@, @DegRevLex@, @Lex@, @Xel@?
Also remove @Vector@, @ToPos@, @PosTo@? -
- There is a lot of cruft in @cocoa5.el@; most of it should be removed!
There are many commented out keywords in @co... -
- I think using the @rotate-split@ function is probably the best solution; it is quite general and might even be useful...
-
- I think the default should be horizontal.
I can make the hor/ver toggle available in the menu.
It can be set for all ... -
- I found the following nice Emacs function...
-
- Here are some emacs fns which might be useful:
@window-body-width@ width of the text area
@window-body-height@ hei... -
- Here are some other design ideas
# make the current functions choose automatically between vert/horiz split (_e.g._ ... -
- Here is a function which works a bit like @M-x cocoa5@ but makes a horizontal split:...
-
- The students in Alg Comp would like to be able to have CoCoA source file on the left, and the running interpreter on ...
10 Mar 2014
-
- The online manual page for *@It@* is hard to read....
09 Mar 2014
-
- I think the problem is the call on line @cocoa5.el:489@:...
-
- Semicolon sometimes does strange things.
It places the cursor in the wrong place if you type semicolon immediately... -
- Here is an idea (silly?)
We could add the new keyword @|->@ which has the same semantics as @Return@. This would ... -
- One post I read suggested that @cocoa5-abbrev-table@ should be @cocoa5-mode-abbrev-table@. Investigate and decide.
-
- One possible solution is to forcibly load the @.abbrev_defs@ file *before* loading @cocoa5@ mode. I believe thsi can...
-
- I changed my @cocoa5.el@ file and was surprised to find that some keywords which have now been removed were still rec...
07 Mar 2014
-
- No problems reported in the last 9 months, so closing.
-
- The regexp...
-
- Here is are two test cases. The first works OK; the second does not....
-
- I now have a new regexp which seems to work better:...
-
- My regexp doesn't work quite as I hoped: it fails of the matching start keyword is on the same line as point. Here's...
-
- I have added a regexp "suffix" so that keywords are recognised "outside strings".
Here is the regexp... -
- I can't remember. Now I cannot reproduce what problem I managed to invent when there was no manual ;-)
Maybe it was...
06 Mar 2014
-
- I believe the relevant function is @cocoa5-close-block@. The bug probably lies inside @cocoa5-last-unended-begin@ (d...
-
- I want some guidance about which fonts to use in the description of a CoCoA function when refering to the arguments. ...
-
- Can I have some details???
-
- I don't believe this issue is so important, but it is worth recording (maybe some @Makefile@ magician will spot the p...
-
- I observed a failed build of the C5 GUI (on Mac OS X 10.5.8). The commands I ran were:...
05 Mar 2014
-
- CoCoA-4 manual had a part with the list of commands and a part with "topics" (the latter has been obsolete for ages!)...
-
- JAA has revised the manual page for the logical operators.
-
- One possible solution is to supply an "impossible name" for those indets we want to be "anonymous".
An impossible ... -
- Added code to handle the special cases of @GenRepr(INT,IDEAL)@ and @GenRepr(RAT,IDEAL)@
Which other fns need simil... -
-
- After talking to Anna about my doubt, we have decided that an empty list in input should produce an error (as it seem...
-
- Neither Anna nor I recall how to reproduce this bug; maybe we have fixed it unwittingly?
Anyway, there is a work-aro...
04 Mar 2014
-
- fixed.
I just added CleanupLine in ... -
- Mostly done. Even cleaned up the code.
There is one function left called "E".
what to do with that? is that useful... -
- Now I'm unsure whether @IsFactorClosed([])@ should return @true@ or give error.
This morning I'm more inclined to fa...
03 Mar 2014
-
- Hey! Have you been talking to Elisa Businelli again?
Fixed the case of an empty list -- it gives *true* (same as th... -
- In the manual we can have...
-
- I think it looks pretty nice now. I even wrote a bit of documentation.
Feedback.
-
- I renamed all functions so they start with @cocoa5-@
I'll leave this in feedback just to make sure no mismatch comes... -
- Seems OK. I'm closing this (unless future guinea-pigs resurrects it ;-)
-
-
- I'd like to use the @interpolate@ fn in one of mys first lessons; can it be implememnted in time? May be related to ...
-
- C5 does not allow computing @GenRepr(1, I)@ because it wants a @RINGELEM@ where I supplied the value @1@ which has ty...
28 Feb 2014
-
- I think I made a fool of myself: we cannot have anonymous symbols in CoCoA because we do not have symbols. (we just ...
-
- I'm already writing the code (taking some rust off my C++) and I'll wait for JAA's approval ;-)
-
- In CoCoALib there are functions for making anonynous symbols (i.e. name of indeterminates).
Should we port them to C... -
27 Feb 2014
-
- I wonder if the next version should be 5.1 instead of 5.0.4; the reason for the jump is the removal of the keywords *...
26 Feb 2014
-
- Can we complete/close any of these issues?
#20, #32, #78, #94, #104, #197, #200, #204, #216, #239, #322
I'm sure the... -
- Things to do (no special order):
* (@Anna) check the roadmap, and see which tasks we can reasonably complete, and wh... -
- Just an issue to gather together all the things to do for the imminent 5.0.9 release.
JAA is hoping the release wi... -
- JAA should respond!
-
- Has this effectively been resolved? It's been ages since I've seen the problem (but I hardly ever use the GUI...)
... -
- Here is a reason why I prefer a built-in fn for increasing max stack height over a command line option: a user discov...
-
- I tried swapping two long lists (10000000 entries), and it was pretty quick; so I deduce that the values are not copi...
Also available in: Atom