Activity
From 17 Jun 2014 to 16 Jul 2014
16 Jul 2014
- 19:01 CoCoA-5 Bug #524: BuiltInFunctions: remove calls to WrongTypeException
- Done BaseRing. I'll do the rest tomorrow
- 16:18 CoCoALib Feature #72: MatByRows, MatByCols
- Not yet entirely convinced about renaming @MakeMatByRows@. It is very similar to @MatByRows@ *but* there is an impor...
- 16:01 CoCoALib Feature #72: MatByRows, MatByCols
- should we rename the CoCoA-5 functions -Make-@MatByRows@?
(and move the "Make.." into obsolescent?) - 14:57 CoCoALib Feature #72 (Feedback): MatByRows, MatByCols
- The code is already there (and has been for how long?) Fns are @MatByRows@ and @MatByCols@.
I added some documentat... - 15:51 CoCoA-5 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 CoCoA-5 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 CoCoA-5 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 CoCoA-5 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 CoCoA-5 Support #488: CoCoAManual: Help page for porting old C4 code to C5
- OK
- 12:44 CoCoA-5 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... - 14:42 CoCoALib Bug #264: Compilation problem with "degree.H" (inline fn defns)
- This seems to be *very similar* to the issue #591; I believe they are occurrences of the same phenomenon. Added #591...
- 14:38 CoCoALib Feature #564: Temporary file for experimentation
- Now that I have added checks for new files in @include/CoCoA/@ and in @src/AlgebraicCore/@, it may be less important ...
- 14:14 CoCoALib Bug #591: Problem with template instantiation and order of include directives
- Clang 3.0 on my computer gives no error.
- 14:07 CoCoALib Bug #591: Problem with template instantiation and order of include directives
- JAA failed to find anything helpful on the internet.
I'm just hoping that the solution of moving the @#include@ wi... - 14:05 CoCoALib Bug #591 (In Progress): Problem with template instantiation and order of include directives
- Some versions of g++ (v4.3.2, v4.4.7, v4.6.3) and intel C++ compiler gave errors when compiling @ex-UtilsVector1.C@ i...
- 12:32 CoCoA-5 Bug #566 (Closed): Online help: problem with "<>"
- 12:27 CoCoA-5 Feature #590 (Closed): package for subalgebras
- In cocoa-4 there was a package to compute with subalgebras.
Restore it.
15 Jul 2014
- 18:17 CoCoALib Feature #589 (New): Implement gin (generic initial ideal) in cocoalib
- available now for cocoa-5 in package.
Implement it in cocoalib
- 18:14 CoCoA-5 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 CoCoA-5 Feature #588 (Closed): Resume code for "gin" (generic initial ideal)
- Resurrect code for "gin", and implement it in cocoalib
- 15:12 CoCoALib Support #252: Documentation for tmp.H (utils on vectors and other containers)
- John Abbott wrote:
> Christof does not like the name @UtilsTemplates.H@; he suggested @UtilsContainers.H@ or @UtilsVe... - 14:47 CoCoALib Support #252: Documentation for tmp.H (utils on vectors and other containers)
- Christof does not like the name @UtilsTemplates.H@; he suggested @UtilsContainers.H@ or @UtilsVector.H@ saying that i...
- 15:08 CoCoALib Design #582: Error codes: use same code for "not poly ring" and "not elem poly ring"
- Just not to lose it in a mountain of archived emails, here is the decisive message:...
- 14:38 CoCoA-5 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 CoCoA-5 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 CoCoA-5 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... - 13:40 CoCoALib Feature #586: BigInt ctor from a machine integer
- There were no objections (in the last 24 hours), so I'll check in. If any problems arise, it's trivial to revert the...
- 12:27 CoCoA-5 Design #525 (Feedback): BuiltInFunctions: evalArgAsT1OrT2, evalArgAsT1OrT2OrT3, ... last argument
- cvs-ed
- 11:02 CoCoA-5 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:22 CoCoALib Feature #304: Module ordering and grading (and shifts)
- I made some tests (and checked with Hilbert series) and it seems that shifts are done and OK. Added some documentation.
- 18:17 CoCoA-5 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:13 CoCoALib Design #432: Semantics of IsPrintedWithMinus
- If we use the definition I gave in comment 1 then some twin-float numbers will be recognized as rationals and should ...
- 18:09 CoCoA-5 Design #493 (Feedback): Cleanup Hilbert package hp.cpkg5
- resurrected and documented functions *HilbertSeriesShifts* and *HilbertSeriesMultiDeg*
they are just shortcuts to av... - 17:53 CoCoALib Support #252: Documentation for tmp.H (utils on vectors and other containers)
- @HasUniqueOwner@ should now work with any container. Checked in.
[I haven't actually made any specific tests, but t... - 17:49 CoCoALib Support #252: Documentation for tmp.H (utils on vectors and other containers)
- I suppose it makes sense to move them... perhaps I'll think about it overnight before acting.
- 17:32 CoCoALib Support #252: Documentation for tmp.H (utils on vectors and other containers)
- Should also << for vector/list be here?
(now it is in io.H)
- 17:23 CoCoALib Support #252 (Feedback): Documentation for tmp.H (utils on vectors and other containers)
- Renamed file to *@UtilsTemplate.H@*.
Moved @LexCmp3@ into the file (from @utils.H@).
Added doc (& moved doc for @Le... - 15:07 CoCoALib Design #415: Remove AsPolyRing etc?
- nice! :-)
some builtin functions are now oneliners
(cvs-ed) - 14:39 CoCoALib Feature #565 (In Progress): FloatApprox for TwinFloat values?
- After further thought it seemed to make more sense to output the twin-float value as a @MantExp2@ structure, which be...
- 14:34 CoCoALib Support #452: Documentation for adding functions to CoCoA-5 (BuiltInFunctions and BuiltInOneLiners)
- not final, but much improved (cvs-ed)
- 14:25 CoCoALib Feature #586: BigInt ctor from a machine integer
- I suggest that I check in the version of @BigInt.H@ that I have (with the ctor from @MachineInt@ being implicit). Th...
- 14:03 CoCoALib Feature #585 (Feedback): (Hilbert-) quasi-polynomials
- Implemented; tested; documented; checked in. So status-->FEEDBACK!
- 13:34 CoCoALib Feature #580: Example for PPVector: ex-PPVector
- I have done a little tidying in @ex-PPVector1.C@.
- 11:09 CoCoALib Feature #580 (Feedback): Example for PPVector: ex-PPVector
- 10:39 CoCoALib Feature #587 (Closed): port to CoCoALib: Homomorphism pkg (ker, IsInjective, IsSurjective..)
- Translate the package @HomomorphismFns.cpkg5@ into CoCoALib.
The related "utility representation" of a homomorphism ... - 10:32 CoCoA-5 Feature #273 (Feedback): Package for Polynomial Algebra Homomorphisms
- checked in documentation.
Next step (new issue): port it into cocoalib.
- 09:26 CoCoA-5 Feature #484: Evaluate in other ring (was called :: in CoCoA-4)
- *ReadExpr* documented, cvs-ed
(updated entry for RingElem) - 08:22 CoCoA-5 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...
11 Jul 2014
- 15:42 CoCoALib Feature #586 (In Progress): BigInt ctor from a machine integer
- Advantages:
* in @IntOperations@ and @NumTheory@ we can reduce the number of signatures to some functions (_e.g._ @Is... - 15:26 CoCoALib Feature #586: BigInt ctor from a machine integer
- I've just removed the @explicit@ keyword from the @BigInt@ ctor. CoCoALib compiled fine (no problems with ambiguity)...
- 15:23 CoCoALib Feature #586 (Rejected): BigInt ctor from a machine integer
- Christof asks why the ctor for a @BigInt@ from a machine integer is @explicit@ rather than implicit.
He also suggest... - 14:35 CoCoA-5 Feature #273: Package for Polynomial Algebra Homomorphisms
- - cleaned up into a package
- tests included in Makefile
- documentation still missing (should be just a minor fix ... - 14:26 CoCoALib Bug #190: Subtle ref count bug for poly rings (via CoeffEmbeddingHom)
- Last night I had this idea, does it work?
The problem is:
*RingHom* 's are refcounted objects, many actually "live" i... - 12:05 CoCoALib Feature #165 (Closed): FractionField -- only of TrueGCDDomain?
- Here's the conclusion:
* currently FrF only of true GCD domain allowed
* the fn *@IsFractionFieldOfGCDDomain@* has ...
10 Jul 2014
- 17:03 CoCoALib Design #308: Error: ERR::NotNonZero instead of ERR::ZeroRingElem? [--> ReqNonZero]
- John Abbott wrote:
> Of those two I have a preference for *@WantNonZero@* -- I can "say" it more easily in my mind t... - 16:01 CoCoALib Design #308: Error: ERR::NotNonZero instead of ERR::ZeroRingElem? [--> ReqNonZero]
- Of those two I have a preference for *@WantNonZero@* -- I can "say" it more easily in my mind than @ExpectNonZero@.
... - 16:52 CoCoALib Design #584 (Resolved): BaseRing for all rings
- I have just noticed that the function which says over which a ring a matrix lies is called *@BaseRing@*. I'm not so ...
- 16:15 CoCoALib Feature #554 (In Progress): CoCoALib-Normaliz interface: cannot print a cone
- 16:14 CoCoALib Feature #554: CoCoALib-Normaliz interface: cannot print a cone
- Implemented some printing. A newly created cone now is printed like:...
- 15:32 CoCoALib Design #415 (Feedback): Remove AsPolyRing etc?
- I've updated the documentation (removed references to @AsPolyRing@ etc.)
tests: I can't really test a function I'v... - 14:26 CoCoALib Feature #568 (Closed): Valid symbol heads
- No problems have come up, so closing.
- 13:45 CoCoALib Feature #125 (In Progress): Matrix equation solving; linear system solving
- 13:41 CoCoALib Feature #585 (Closed): (Hilbert-) quasi-polynomials
- For objects (cones, algebras,..) which are not generated in degree 1 the Hilbert function is not a polynomial anymore...
- 13:38 CoCoALib Feature #223 (Closed): Automatic mapping of RingElems
- Closing this issue, but leaving #7 open. This is fine as far as it goes.
- 13:35 Support #425 (Closed): Osnabrueck 2014-01
- Essentially everything listed has been done --> closing.
- 13:33 Bug #238 (Closed): Cleaner CVS?
- 13:32 Bug #238: Cleaner CVS?
- Closing.
09 Jul 2014
- 18:37 CoCoALib Design #308: Error: ERR::NotNonZero instead of ERR::ZeroRingElem? [--> ReqNonZero]
- *WantNonZero* or
*ExpectNonZero* - 18:30 CoCoALib Design #308: Error: ERR::NotNonZero instead of ERR::ZeroRingElem? [--> ReqNonZero]
- Here are some other candidate names:
*RequireNonZero*
*ReqNonZero*
*NeedNonZero*
*MustBeNonZero*
*WantNonZero*
- 18:25 CoCoALib Design #308: Error: ERR::NotNonZero instead of ERR::ZeroRingElem? [--> ReqNonZero]
- Well, this is actually a sub-task.
I think we can make a quick decision about the names (we have already talked abou... - 18:14 CoCoALib Design #308: Error: ERR::NotNonZero instead of ERR::ZeroRingElem? [--> ReqNonZero]
- This task is really already covered by the proposed radical restructuring and renaming of the error codes #427. As a...
- 18:19 CoCoALib Feature #165: FractionField -- only of TrueGCDDomain?
- I think we'd better be conservative, i.e. only for true GCDRings.
If someone ever asks for the general case then we ... - 18:11 CoCoALib Feature #165: FractionField -- only of TrueGCDDomain?
- Can this be closed in the near future? (i.e. before Seoul)
- 18:15 CoCoALib Bug #264 (Closed): Compilation problem with "degree.H" (inline fn defns)
- No problem has ever occurred to anyone in the last year.
Have we fixed it? can't remember.
Has the compiler changed... - 17:59 CoCoALib Bug #264: Compilation problem with "degree.H" (inline fn defns)
- *@Anna* Is this still a problem? I hope not; then we can just terminate the issue.
- 17:54 CoCoALib Feature #554: CoCoALib-Normaliz interface: cannot print a cone
- Maybe we can resolve this issue while I'm in Osnabrueck?
- 17:50 CoCoALib Design #415: Remove AsPolyRing etc?
- I have removed @AsDenseUPolyRing@, @AsFreeModule@ and @AsFGModule@.
The code compiles and all tests pass, so I have ...
08 Jul 2014
- 17:49 CoCoALib Design #415: Remove AsPolyRing etc?
- I've now removed @AsQuotientRing@, and revised the imple of @BaseRing@ (see #584)
- 11:17 CoCoALib Design #415: Remove AsPolyRing etc?
- I've removed @AsPolyRing@, @AsSparsePolyRing@ and @AsFractionField@.
So far so good. Some bits of code have becom... - 17:48 CoCoALib Design #584: BaseRing for all rings
- I've implemented it, and it seems to work. Currently the impl does *(B)*, but it'd be easy to change to *(A)*.
(2014... - 11:43 CoCoALib Design #584: BaseRing for all rings
- Not sure what @BaseRing(ZZ)@ should produce:
*(A)* either @ZZ@ itself
*(B)* an error
My current preference (afte... - 11:41 CoCoALib Design #584: BaseRing for all rings
- One problem with this approach is that we would exclude product rings, since a product ring could have several "paren...
- 11:38 CoCoALib Design #584 (Closed): BaseRing for all rings
- I'm considering implementing @BaseRing@ for all rings (except perhaps @ZZ@).
With our current design every ring ha...
07 Jul 2014
- 11:48 CoCoALib Feature #583 (New): New function for printing with extra information
- In CoCoA-5 we have the command *@Describe@* for printing a detailed description of an object.
It would be useful to ... - 09:36 CoCoALib Design #582: Error codes: use same code for "not poly ring" and "not elem poly ring"
- John Abbott wrote:
> (A) @Expected (element of) PolyRing@
this one!
- 09:29 CoCoALib Design #582: Error codes: use same code for "not poly ring" and "not elem poly ring"
- See also emails exchanged on 20140704 with subject "Opinion".
We need suitable wording for the combined error: how... - 09:25 CoCoALib Design #582 (New): Error codes: use same code for "not poly ring" and "not elem poly ring"
- Proposal: merge the two error codes @NotPolyRing@ and @NotElemPolyRing@.
Reasons:
(1) the distinction is really q...
04 Jul 2014
- 14:40 CoCoALib Design #581: C++14: MachineInt
- It might be possible to use templates for the ctors of @MachineInt@ together with a mechanism for ensuring that the a...
- 14:36 CoCoALib Design #581 (Closed): C++14: MachineInt
- We must modify @MachineInt@ when switiching to C++14 because there is a new integral type: @(unsigned) long long@
- 12:12 CoCoA-5 Support #548: Printing rings with ID
- John Abbott wrote:
> Should this issue be in CoCoA-5 or CoCoALib?
I think it can stay in CoCoA-5 because it is ea... - 11:39 CoCoA-5 Support #548: Printing rings with ID
- Should this issue be in CoCoA-5 or CoCoALib?
You are right that there is no global register of rings currently. W... - 10:50 CoCoA-5 Support #548: Printing rings with ID
- John Abbott wrote:
> I'm still not happy with the name of @RingID@; the name makes me think that it *gets* the ID fr...
03 Jul 2014
- 13:28 CoCoA-5 Support #548: Printing rings with ID
- I'm still not happy with the name of @RingID@; the name makes me think that it *gets* the ID from a ring, rather than...
- 11:41 CoCoA-5 Support #548: Printing rings with ID
- added function ID for RING
- 11:29 CoCoA-5 Support #548: Printing rings with ID
- what about this: (verbose, but not more than before the ID change)
I like it! .... but there is the problem of too m... - 09:05 CoCoA-5 Support #548: Printing rings with ID
- John Abbott wrote:
> Yesterday Christof suggested that @ZZ@ and @QQ@ should always be printed that way (rather than ... - 08:56 CoCoA-5 Support #548: Printing rings with ID
- Yesterday Christof suggested that @ZZ@ and @QQ@ should always be printed that way (rather than @ring(0)@ and @ring(1)...
- 08:40 CoCoA-5 Support #548: Printing rings with ID
- fixed all tests, but we should still discuss on the output.
For example ... - 08:32 CoCoALib Feature #580 (Resolved): Example for PPVector: ex-PPVector
- resurrected old example, improved, cvs-ed
02 Jul 2014
- 18:42 CoCoA-5 Support #548: Printing rings with ID
- mostly done.... now I should update all the failing tests.... tomorrow
- 17:21 CoCoA-5 Support #548: Printing rings with ID
- John Abbott wrote:
> allow @RingID@ to have an optional second arg which is a string giving some info about the ring ... - 17:19 CoCoA-5 Support #548: Printing rings with ID
- Talked about this with Christof. Here's an idea we had:
allow @RingID@ to have an optional second arg which is a st... - 16:54 CoCoA-5 Design #532 (Closed): New package: OBSOLESCENT
- 16:45 CoCoA-5 Support #456: CoCoAManual: New structure for manual?
- Strictly related with #177
- 16:40 CoCoA-5 Support #177: CoCoAManual: General part of the documentation is obsolete: update? discard?
- This was a very general issue: now split in more issues (mostly already closed in 5.1.0)
- 16:29 CoCoA-5 Bug #34 (Resolved): CoCoAManual: obsolete entries in the manual
- I added the key "obsolete".
now ... - 16:11 CoCoA-5 Design #567 (Closed): Emacs UI: coloured syntax in output buffer has problems if error message shows a single double-quote
- No comments so another quick check and ... closing!
- 16:08 CoCoA-5 Bug #566 (Feedback): Online help: problem with "<>"
- it's fine for me too... maybe we changed the code for some other reason and fixed this as a side effect.
- 16:03 CoCoA-5 Bug #397 (Closed): EMACS UI: fix windows splitting
- This is discussed (and solved) in #464
Instead of trying to be clever now there are two entries in the CoCoA-5 menu ... - 14:31 CoCoA-5 Feature #561: Emacs UI: unrecognized keywords (ImportByValue...)
- fixed @ImportBy..@ and also @package@ (lower-case)
major cleaning of keyword strings (so that they almost none is wr... - 14:28 CoCoALib Feature #580 (Closed): Example for PPVector: ex-PPVector
- The doc for @PPVector@ refers to an example, @ex-PPVector.C@, but no such file exists.
- 11:47 CoCoA-5 Feature #579 (In Progress): Prototype package for Linear Commutative Algebra
- Write a prototype package for the algorithms described in the new Kreuzer-Robbiano book.
[related with Elisa Palezza... - 11:43 CoCoA-5 Support #398 (Closed): Resurrect Relnotes()
01 Jul 2014
- 17:09 CoCoA-5 Feature #578 (In Progress): Gaussian Elimination
- The procedures @SwapRows@ and @SetRow@ were already available.
Now they are in the manual. - 17:06 CoCoA-5 Feature #578 (In Progress): Gaussian Elimination
- In CoCoALib we have some functions for Gaussian Elimination.
Choose which and how to make them available at CoCoA-5 ... - 17:02 CoCoA-5 Feature #464 (Feedback): Emacs UI: split horizontally instead of vertically?
- 17:02 CoCoA-5 Feature #464: Emacs UI: split horizontally instead of vertically?
- I slightly improved the menu so that it indicates which splitting is defined.
(with a tick next to side-by-side or t... - 14:34 CoCoALib Bug #577 (Feedback): Hilbert crashes with > 100 indeterminates
- fixed. Now using @CopyHPPower@ (copies the precomputed value or computes the correct one) instead of @HPPowerList@ (...
- 14:04 CoCoALib Bug #577: Hilbert crashes with > 100 indeterminates
- (sorry, I meant "101")
I found where the problem is (a hard limit = 100 in GlobalManager) and I am fixing it.
- 13:34 CoCoALib Bug #577: Hilbert crashes with > 100 indeterminates
- I've just tried with my own "local" copy of C5; seems to work fine (even trying several times).
Platform is MacOSX 1... - 12:42 CoCoALib Bug #577 (Closed): Hilbert crashes with > 100 indeterminates
- ...
28 Jun 2014
- 20:48 CoCoA-5 Feature #464 (Resolved): Emacs UI: split horizontally instead of vertically?
- I think I fixed the "random" behaviour for the window splitting.
I added the choice in the CoCoA-5 menu and the flag...
26 Jun 2014
- 16:54 CoCoALib Support #302: Compilation on M$Windows: Visual Studio
- I tried the newest cvs version and CoCoALib does compile in 32 and 64 bit. I only had to change what I have reported ...
- 15:33 CoCoA-5 Design #576 (Closed): Disallow juxtaposition for string literals?
- If there were any serious problems, they'd have come to light by now (almost 24 hours of testing!)
Closing.
- 12:27 CoCoA-5 Design #576: Disallow juxtaposition for string literals?
- > All in all, it really does seem to be a "useless" feature...
and was not in CoCoA-4. It's a pointless exception.
- 12:12 CoCoA-5 Design #576: Disallow juxtaposition for string literals?
- Here is a possible reason for wanting to allow juxtaposition of strings: if an input includes a very long string lite...
- 15:14 CoCoA-5 Support #548: Printing rings with ID
- How will rings be printed in resolutions?
I recall that CoCoA used a syntax like @ring#7@; we could do this (but i... - 15:11 CoCoA-5 Bug #182 (Closed): Unescaped double quote inside superstring
- This bug essentially vanished when we abolished multiline string literals.
Now that juxtaposed strings literals ar... - 12:06 CoCoA-5 Bug #182: Unescaped double quote inside superstring
- I have (temporarily?) disabled recognition of juxtaposed strings. The resulting behaviour on the example input is:
... - 12:03 CoCoA-5 Feature #464: Emacs UI: split horizontally instead of vertically?
- OK for a menu flag which indicates the preferred way of splitting.
Some while ago I added to @cocoa5.el@ the fn @c... - 08:24 CoCoA-5 Feature #464: Emacs UI: split horizontally instead of vertically?
- Apparently (on Aquamacs) it splits horizontally or vertically depending on the width of the window. That may be conf...
- 08:18 CoCoA-5 Support #559: Release: CoCoA-5.1.0
- Almost all done. still missing: gui on windows
25 Jun 2014
- 19:16 CoCoA-5 Design #576: Disallow juxtaposition for string literals?
- I tried; it compiled and all tests pass. Will test more tomorrow, and then check in.
- 17:04 CoCoA-5 Design #576 (In Progress): Disallow juxtaposition for string literals?
- I believe the relevant source is in @Parser.C@ lines 2095-2103 inclusive.
I'll try commenting out, and see if everyt... - 16:50 CoCoA-5 Design #576: Disallow juxtaposition for string literals?
- > Can we remove this "feature? What was the original reason for wanting this?
The original reason was to allow it ... - 15:01 CoCoA-5 Design #576 (Closed): Disallow juxtaposition for string literals?
- Currently CoCoA-5 accepts juxtaposed string literals (_i.e._ separated by nothing or white space).
Can we remove t... - 15:50 CoCoA-5 Bug #164 (Feedback): CoCoA-5 emacs interface bug (minor): Source & SourceRegion with troublesome filenames
- I have modified @cocoa5.el@ to add escapes for @"@ and newlines inside filenames.
A quick test showed that it works a... - 13:14 CoCoA-5 Support #548: Printing rings with ID
- The name @RingWithID@ is longer than I would like; I originally suggested @ring(3)@ but that is not so clear. Maybe ...
- 13:09 CoCoA-5 Support #548: Printing rings with ID
- If we go with the idea of printing simply @RingWithID(...)@ then I presume the @describe@ command should fully descri...
- 12:52 CoCoA-5 Bug #182 (In Progress): Unescaped double quote inside superstring
- If I recall correctly, we abolished "superstrings" in CoCoA-5.1. So the problem is no longer relevant. In any case,...
- 12:16 CoCoALib Feature #571 (Feedback): CmpAbs for RingElem
- I have now added a new test, @test-RingElem4@, for @CmpAbs@ of @RingElem@. Will check in.
24 Jun 2014
- 10:36 CoCoA-5 Bug #279: Bug in Radical (actually a RingHom problem)
- Here is an excerpt from CoCoA (this morning, 20140624)...
23 Jun 2014
- 17:40 CoCoALib Feature #575 (In Progress): Investigate using cmake for configuration
- Christof is still trying to make @cmake@ behave well on MacOS; both static and dynamic libraries give (different) pro...
- 17:34 CoCoALib Feature #573: Use symbolic links for external libraries
- The symbolic link approach now seems to be working -- I even tried with a nasty directory name apparently without mis...
20 Jun 2014
- 15:00 CoCoALib Feature #575: Investigate using cmake for configuration
- John Abbott wrote:
> *Bad* it is not clear how to specify a custom "installation" of GMP instead of the standard sys... - 09:18 CoCoALib Feature #575: Investigate using cmake for configuration
- Christof has been investigating using @cmake@ for configuring normaliz/libnormaliz.
*Good* @cmake@ seems to handle... - 09:10 CoCoALib Feature #575 (In Progress): Investigate using cmake for configuration
- The @cmake@ program offers a platform independent "configuration" mechanism. In principle it could replace CoCoA's e...
19 Jun 2014
- 17:53 CoCoALib Feature #573: Use symbolic links for external libraries
- I thought I could be clever in @autoconf.mk@ and use @-lgsl@, @-lfrobby@ and so on.
*But* the linker does some strang... - 17:00 CoCoALib Feature #573: Use symbolic links for external libraries
- Here's a quite summary of the current situation (created entirely manually so far).
There's a new directory @configu... - 15:27 CoCoALib Feature #573: Use symbolic links for external libraries
- John Abbott wrote:
> I now think that the correct place for the external library directory is in @configuration/@.
... - 15:15 CoCoALib Feature #573 (In Progress): Use symbolic links for external libraries
- I now think that the correct place for the external library directory is in @configuration/@.
It may as well be ca... - 11:22 CoCoALib Support #574 (Closed): Tidy CoCoA root directory
- There are too many files/directories in the CoCoA root directory.
I think we can remove the GPLv2 file since there i...
18 Jun 2014
- 12:03 CoCoALib Feature #573 (Closed): Use symbolic links for external libraries
- To avoid problems with "awkward" path names to external libraries, I suggest creating symbolic links (with nice names...
Also available in: Atom