Activity
From 13 Jul 2014 to 11 Aug 2014
01 Aug 2014
- 10:56 Feature #484: Evaluate in other ring (was called :: in CoCoA-4)
- the CoCoA-4 operator "::" is now in another specific issue.
For the time being I think that *ReadExpr* may be good e... - 10:54 Feature #484 (Feedback): Evaluate in other ring (was called :: in CoCoA-4)
- 10:53 Feature #606 (Closed): Evaluate in ring operator (was called :: in CoCoA-4)
- CoCoA-4 has the *@::@* operator which evaluated expressions in a given ring:...
- 10:36 Support #605 (Closed): Release: CoCoA-5.1.1
- Everything for the release
finalize cvs
make
make doc
make ManExamples
in snapshot dir:
cd src/CoCoA-5/re... - 09:41 Feature #603 (Closed): Resume CheckArgTypes
- Done, tested, documented
Different from the cocoa-4 version: more flexible (see manual) - 09:39 Feature #603 (Closed): Resume CheckArgTypes
- Redesign CoCoA-4 function CheckArgTypes (for checking argument types, of course...)
31 Jul 2014
- 17:36 Support #325: CoCoAManual: display syntax first
- Even though I had closed this issue saying:
> Even though CoCoAHelp.xml isn't all written like that (too dangerous t... - 15:15 Support #324 (Closed): Correct font for variable references in description
- Duplicates #169: "Font for parameters in manual".
Design is all set there.
Closing this issue. - 15:13 Support #169 (In Progress): Font for parameters in manual
- As said in another issue:
- parameters should have the same name as in <syntax>
- <syntax> should be moved before <... - 15:08 Design #294 (Resolved): BuiltInFunctions: General "OneLiner" for arguments of different type
- Is the new approach in BuiltInFunctions good enough?
I think so: it is not a one-liner but it's very readable (look f... - 15:06 Design #493 (Closed): Cleanup Hilbert package hp.cpkg5
- Now all functions work. A proper clean-up and re-design is in another issue.
30 Jul 2014
- 17:29 Feature #600: efficient subalgebras
- We are also working an efficient algorithm for implicitization.
Keep that in mind for this issue, or make a new issue. - 17:23 Feature #600 (New): efficient subalgebras
- There are many tools to deal with subalgebras (see @toric@ and @normaliz@), so it would make sense to design a nice i...
- 17:22 Feature #590 (Feedback): package for subalgebras
- Resumed package (slight design change, documented)
It will be imrpoved, but that's beyond this task scope.
- 17:20 Feature #359: RingOf for list
- The function in CoCoA-5 is already done and called @RingSet@ (see manual) but I'm not happy with the name: should I c...
29 Jul 2014
- 16:26 Design #403: Misuse of dot-dot operator
- the error message was indeed a bit puzzling in some cases now it is:...
- 12:31 Design #403: Misuse of dot-dot operator
- Giulia's problem could be neatly resolved by allowing the following syntax *@L[2..4]@* to mean @[L[k] | k in 2..4]@. ...
- 12:04 Design #403 (Rejected): Misuse of dot-dot operator
- My main concern is the (possibly) unexpected behaviour illustrated in example *@(B)@* in comment 1. However, for a l...
- 11:54 Design #403: Misuse of dot-dot operator
- The main action taken was to clarify the manual entry for ".."; it is now quite clear, and even mentions Giulia's inc...
- 07:28 Design #403: Misuse of dot-dot operator
- I suggest to reject this issue.
@A..B@ works for A and B integers or indeterminates in the order of their definition... - 09:31 Feature #273 (Closed): Package for Polynomial Algebra Homomorphisms
- 09:29 Feature #484 (In Progress): Evaluate in other ring (was called :: in CoCoA-4)
28 Jul 2014
- 21:50 Bug #382 (Closed): Subtle bug with CoeffEmbeddingHom
- This is no longer a problem (after resolving issue #190). Closing.
PS I have added the example to @exbugs.cocoa5@. - 17:48 Feature #173 (Rejected): Anonymous symbols: should they be available in CoCoA-5?
- 17:44 Feature #20 (Closed): How to get the compilation flags of CoCoA-5?
- Compilations flags are given by @VersionInfo()@
- 17:41 Design #412: intersection (all lower case)
- The clean solution would be to have @intersect@ doing what @Intersection@ used to do.
Problem is @intersect@ for IDE... - 17:12 Slug #99 (Feedback): Function "insert": obsolescent
- Documented as obsolescent
- 17:01 Feature #25: Function "Call"
- It is now officially documented as OBSOLETE, so I close this issue.
- 16:44 Feature #485: Initialization for CoCoA-5: file init.cocoa5
- the general @init@ file now works well.
I don't think there is a particular need for a user init file.
I regard thi... - 16:35 Feature #330 (Closed): Syzygy for modules: homogeneous module
- 16:28 Design #476: Review utility of package IO
- I don't think we should eliminate it.
In time, we can see what can be useful and advertized (low priority) - 16:20 Feature #512: Resurrect MakeCheck()
- Undecided, needs more thinking. Not urgent
- 11:48 Design #597 (New): Interpreter.C: remove calls to WrongTypeException
- 11:48 Bug #524 (Closed): BuiltInFunctions: remove calls to WrongTypeException
- There are a few more @WrongTypeException@ left in @Interpreter.C@.
Those are of a slightly different nature and shou... - 10:55 Design #595: rename BigIntValue, IdealValue --> INTValue, IDEALValue? or even INT, IDEAL?
- Changed also also PtrCast into RefTo<..>
cvs-ed
25 Jul 2014
- 19:50 Design #595: rename BigIntValue, IdealValue --> INTValue, IDEALValue? or even INT, IDEAL?
- added templates for @RefTo<..>@.
- 16:16 Design #595: rename BigIntValue, IdealValue --> INTValue, IDEALValue? or even INT, IDEAL?
- Now all @switch@ following @EvalArgAsT1or...@ have a default case giving and error.
This is good for maintenance: if... - 12:53 Design #595: rename BigIntValue, IdealValue --> INTValue, IDEALValue? or even INT, IDEAL?
- Another possible name is *@UnwrapBigInt@*. I think it conveys the idea that the @BigInt@ is hidden inside the object...
- 09:11 Design #595: rename BigIntValue, IdealValue --> INTValue, IDEALValue? or even INT, IDEAL?
- First pass is mostly done (BigIntValue --> INT, and similar).
I'm a bit undecided about a few other types like @OSTR... - 08:51 Design #595: rename BigIntValue, IdealValue --> INTValue, IDEALValue? or even INT, IDEAL?
- John Abbott wrote:
> I'm not entirely convinced by the names @PtrCastIDEAL@ etc.
> It is true that the arg is a "po... - 08:47 Design #595: rename BigIntValue, IdealValue --> INTValue, IDEALValue? or even INT, IDEAL?
- I started the change: there is no name clash problem with the class @INT@ :-)
... at least with gcc :-/
Anyway: in ca... - 08:19 Support #488: CoCoAManual: Help page for porting old C4 code to C5
- John Abbott wrote:
> I'd like a name which more clearly expresses that it is for converting "old" C4 code to C5.
Ind...
24 Jul 2014
- 21:19 Design #595 (In Progress): rename BigIntValue, IdealValue --> INTValue, IDEALValue? or even INT, IDEAL?
- Certainly the excerpt from @BuiltinOneLiners@ is very clear.
We have already spoken about the use of @default@ in ... - 18:56 Support #488: CoCoAManual: Help page for porting old C4 code to C5
- I'd like a name which more clearly expresses that it is for converting "old" C4 code to C5. We may even need some hi...
- 18:19 Support #488: CoCoAManual: Help page for porting old C4 code to C5
- I went through the translation table and I updated it (almost complete now :-)
.... I was just wondering: should w... - 18:00 Bug #378 (In Progress): Ungraceful behaviour: Source inside For loop
- I found where (I looked for @TT_FOR@, in @Parse.C@) to give a proper error (if we decide to disable it) or to enable ...
- 10:38 Bug #378: Ungraceful behaviour: Source inside For loop
- From Alexandru Costantinescu (who used @source@ in loops in cocoa-4)
> I am using a data base of Hilbert functions, ... - 10:34 Bug #378: Ungraceful behaviour: Source inside For loop
- A few more details: I ran this line...
- 17:52 Feature #579: Prototype package for Linear Commutative Algebra
- First functions 2014-07-23
(MinMult, AlgMult, GeoMult, ...) - 09:56 Feature #596 (Closed): function "packages"
- all done
- 09:55 Feature #596 (Closed): function "packages"
- implement function "packages" for list of loaded packages.
23 Jul 2014
- 12:38 Design #595: rename BigIntValue, IdealValue --> INTValue, IDEALValue? or even INT, IDEAL?
- This is how some lines in @BuiltinOneLiners@ would look...
- 12:30 Design #595 (Closed): rename BigIntValue, IdealValue --> INTValue, IDEALValue? or even INT, IDEAL?
- In the interpreter (@AST.H@) we have the definition of the classes @BlahValue@, for example
@BigIntValue@, @IdealVal...
22 Jul 2014
- 15:59 Bug #594 (Feedback): CharPoly(MAT) and MinPoly(MAT) work in different settings: unify behaviaour
- all done (also documented)
- 12:46 Bug #594 (Closed): CharPoly(MAT) and MinPoly(MAT) work in different settings: unify behaviaour
- They should both work both with M in K or in Kx (but not dependent on x)...
- 12:44 Feature #173: Anonymous symbols: should they be available in CoCoA-5?
- Now I'm incline to say "no" and reject the issue: too much hassle for very little use.
@NewSymbol()/NewSymbols(n)@ a... - 12:38 Feature #492: New C5 fn for adjusting the warning level
- John Abbott wrote:
> This should be easy (but you never know!).
> Moving to after Easter as it is unimportant.
I... - 09:42 Design #491: Cleaning: Cruft in CoCoA-5 packages
- This task will never be closed (when would we ever be able to say that? ;-)
So, let's say that we start deleting obs... - 09:40 Feature #512: Resurrect MakeCheck()
- It should be easy enough to implement if we can get the path of the tests.
This works for me (as an example)... - 09:32 Feature #487: ScalarProduct accepts MatrixRow?
- I think it is possible, but tedious work. Is it worth the effort?
- 09:19 Bug #132: BringIn should allow reduction modulo p
- now works in some cases, e.g. the one in the description ;-)
More precisely it works if the coefficient ring (of the... - 08:47 Design #476: Review utility of package IO
- At the moment it is only exporting @format@ (which I find quite useful).
I updated @Format/format@ and checked the m... - 08:27 Design #546: ideal wants LIST of RINGELEM
- It was easy to fix it for @ideal([x,0,y]);@.
I re-designed the function for @ideal@ a bit.
I renamed @evalArgAsRing... - 07:44 Feature #518 (Feedback): incr/decr functions: to be used in packages
- All done (I think).
If/when we make += it'll be easy to search for incr/decr
21 Jul 2014
- 18:39 Bug #279 (Feedback): Bug in Radical (actually a RingHom problem)
- found the bug: usual ref-count bug on RINGHOM.
Found a few more little bugs in the way ;-)
18 Jul 2014
- 16:08 Feature #518: incr/decr functions: to be used in packages
- John Abbott wrote:
> "incr" is most used in @list.cpkg5@ for @QuickSort1@ and @QuickSortBy1@.
I updated the code ... - 12:55 Bug #543 (Feedback): Interpreter: problem when calling the manual with trailing spaces and comments
- done
- 10:15 Support #522 (Feedback): Manual: duplication in "see also" and "All other matches"
- Seems ok on @round@ and @indets@.
(code in @OnlineHelp@ is pretty horrible, but it works) - 09:06 Bug #524 (Feedback): BuiltInFunctions: remove calls to WrongTypeException
- All done (@ascii@, @apply@, @ContentWRT@, @CoefficientWRT@).
Changed priority to high because I'm presenting this in...
16 Jul 2014
- 19:01 Bug #524: BuiltInFunctions: remove calls to WrongTypeException
- Done BaseRing. I'll do the rest tomorrow
- 15:51 Bug #34: CoCoAManual: obsolete entries in the manual
- Yes, obsolescent functions should give some warning that they are going to disappear (and presumably what to do inste...
- 15:40 Bug #34: CoCoAManual: obsolete entries in the manual
- Remember that obsolescent functions should be moved to the package @obsolescent.cpkg5@.
Now they all works silently.... - 15:37 Bug #34 (Feedback): CoCoAManual: obsolete entries in the manual
- Done. Rule for maintaining it.
(1) Add [OBSOLETE] or [OBSOLESCENT] in the title of obsolete/obsolescent functions, ... - 15:18 Support #488 (Resolved): CoCoAManual: Help page for porting old C4 code to C5
- I set a manual chapter for these kind of information.
It is called <title>Migrating from CoCoA-4 and keeping up-to... - 13:43 Support #488: CoCoAManual: Help page for porting old C4 code to C5
- OK
- 12:44 Support #488: CoCoAManual: Help page for porting old C4 code to C5
- John Abbott wrote:
> I have added a manual page entitled *@updating CoCoA-4 code@*; and another entitled *@CoCoA-4 m... - 12:32 Bug #566 (Closed): Online help: problem with "<>"
- 12:27 Feature #590 (Closed): package for subalgebras
- In cocoa-4 there was a package to compute with subalgebras.
Restore it.
15 Jul 2014
- 18:14 Feature #588 (Feedback): Resume code for "gin" (generic initial ideal)
- Done in package.
Implemented only using twin-floats with range [-10^6, 10^6].
No point in offering more flexibility... - 15:42 Feature #588 (Closed): Resume code for "gin" (generic initial ideal)
- Resurrect code for "gin", and implement it in cocoalib
- 14:38 Bug #34: CoCoAManual: obsolete entries in the manual
- John Abbott wrote:
> I propose adding @OBSOLETE@ (in capitals) as the first word of the title;
I made it all capi... - 13:48 Bug #34: CoCoAManual: obsolete entries in the manual
- I think your suggestion is a good one.
I propose adding @OBSOLETE@ (in capitals) as the first word of the title; t... - 12:37 Bug #34: CoCoAManual: obsolete entries in the manual
- Anna Maria Bigatti wrote:
> I added the key "obsolete".
> now
> [...]
> gives the list of obsolete commands (whi... - 12:27 Design #525 (Feedback): BuiltInFunctions: evalArgAsT1OrT2, evalArgAsT1OrT2OrT3, ... last argument
- cvs-ed
- 11:02 Design #525 (Resolved): BuiltInFunctions: evalArgAsT1OrT2, evalArgAsT1OrT2OrT3, ... last argument
- We agreed that it would be handy to have the same interface for
*evalArgAsT1orT2* and *evalArgAsT1orT2orT3*.
The la...
14 Jul 2014
- 18:17 Support #559 (Closed): Release: CoCoA-5.1.0
- I did this work a long time ago, but never got to deal with the GUI for windows.
No longer makes sense now: going fo... - 18:09 Design #493 (Feedback): Cleanup Hilbert package hp.cpkg5
- resurrected and documented functions *HilbertSeriesShifts* and *HilbertSeriesMultiDeg*
they are just shortcuts to av... - 10:32 Feature #273 (Feedback): Package for Polynomial Algebra Homomorphisms
- checked in documentation.
Next step (new issue): port it into cocoalib.
- 09:26 Feature #484: Evaluate in other ring (was called :: in CoCoA-4)
- *ReadExpr* documented, cvs-ed
(updated entry for RingElem) - 08:22 Feature #484: Evaluate in other ring (was called :: in CoCoA-4)
- In CoCoALib we can read expressions from strings with *ReadExpr(RING, STRING)*.
I'm going to add it to cocoa-5 so you...
Also available in: Atom