Activity
From 11 Jun 2014 to 10 Jul 2014
10 Jul 2014
-
17:03 CoCoALib Design #308: Error: ERR::NotNonZero instead of ERR::ZeroRingElem?
- 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?
- Of those two I have a preference for *@WantNonZero@* -- I can "say" it more easily in my mind than @ExpectNonZero@.
... -
- 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
-
- Implemented some printing. A newly created cone now is printed like:...
-
- I've updated the documentation (removed references to @AsPolyRing@ etc.)
tests: I can't really test a function I'v... -
- No problems have come up, so closing.
-
-
- For objects (cones, algebras,..) which are not generated in degree 1 the Hilbert function is not a polynomial anymore...
-
- Closing this issue, but leaving #7 open. This is fine as far as it goes.
-
- Essentially everything listed has been done --> closing.
-
-
- Closing.
09 Jul 2014
-
- *WantNonZero* or
*ExpectNonZero* -
- Here are some other candidate names:
*RequireNonZero*
*ReqNonZero*
*NeedNonZero*
*MustBeNonZero*
*WantNonZero*
-
- Well, this is actually a sub-task.
I think we can make a quick decision about the names (we have already talked abou... -
- This task is really already covered by the proposed radical restructuring and renaming of the error codes #427. As a...
-
- I think we'd better be conservative, i.e. only for true GCDRings.
If someone ever asks for the general case then we ... -
- Can this be closed in the near future? (i.e. before Seoul)
-
- No problem has ever occurred to anyone in the last year.
Have we fixed it? can't remember.
Has the compiler changed... -
- *@Anna* Is this still a problem? I hope not; then we can just terminate the issue.
-
- Maybe we can resolve this issue while I'm in Osnabrueck?
-
- I have removed @AsDenseUPolyRing@, @AsFreeModule@ and @AsFGModule@.
The code compiles and all tests pass, so I have ...
08 Jul 2014
-
- I've now removed @AsQuotientRing@, and revised the imple of @BaseRing@ (see #584)
-
- I've removed @AsPolyRing@, @AsSparsePolyRing@ and @AsFractionField@.
So far so good. Some bits of code have becom... -
- I've implemented it, and it seems to work. Currently the impl does *(B)*, but it'd be easy to change to *(A)*.
(2014... -
- Not sure what @BaseRing(ZZ)@ should produce:
*(A)* either @ZZ@ itself
*(B)* an error
My current preference (afte... -
- One problem with this approach is that we would exclude product rings, since a product ring could have several "paren...
-
- I'm considering implementing @BaseRing@ for all rings (except perhaps @ZZ@).
With our current design every ring ha...
07 Jul 2014
-
- In CoCoA-5 we have the command *@Describe@* for printing a detailed description of an object.
It would be useful to ... -
- John Abbott wrote:
> (A) @Expected (element of) PolyRing@
this one!
-
- See also emails exchanged on 20140704 with subject "Opinion".
We need suitable wording for the combined error: how... -
- Proposal: merge the two error codes @NotPolyRing@ and @NotElemPolyRing@.
Reasons:
(1) the distinction is really q...
04 Jul 2014
-
- It might be possible to use templates for the ctors of @MachineInt@ together with a mechanism for ensuring that the a...
-
- We must modify @MachineInt@ when switiching to C++14 because there is a new integral type: @(unsigned) long long@
-
- John Abbott wrote:
> Should this issue be in CoCoA-5 or CoCoALib?
I think it can stay in CoCoA-5 because it is ea... -
- Should this issue be in CoCoA-5 or CoCoALib?
You are right that there is no global register of rings currently. W... -
- 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
-
- 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...
-
- added function ID for RING
-
- what about this: (verbose, but not more than before the ID change)
I like it! .... but there is the problem of too m... -
- John Abbott wrote:
> Yesterday Christof suggested that @ZZ@ and @QQ@ should always be printed that way (rather than ... -
- Yesterday Christof suggested that @ZZ@ and @QQ@ should always be printed that way (rather than @ring(0)@ and @ring(1)...
-
- fixed all tests, but we should still discuss on the output.
For example ... -
- resurrected old example, improved, cvs-ed
02 Jul 2014
-
- mostly done.... now I should update all the failing tests.... tomorrow
-
- John Abbott wrote:
> allow @RingID@ to have an optional second arg which is a string giving some info about the ring ... -
- Talked about this with Christof. Here's an idea we had:
allow @RingID@ to have an optional second arg which is a st... -
-
- Strictly related with #177
-
- This was a very general issue: now split in more issues (mostly already closed in 5.1.0)
-
- I added the key "obsolete".
now ... -
- No comments so another quick check and ... closing!
-
- it's fine for me too... maybe we changed the code for some other reason and fixed this as a side effect.
-
- This is discussed (and solved) in #464
Instead of trying to be clever now there are two entries in the CoCoA-5 menu ... -
- fixed @ImportBy..@ and also @package@ (lower-case)
major cleaning of keyword strings (so that they almost none is wr... -
- The doc for @PPVector@ refers to an example, @ex-PPVector.C@, but no such file exists.
-
- Write a prototype package for the algorithms described in the new Kreuzer-Robbiano book.
[related with Elisa Palezza... -
01 Jul 2014
-
- The procedures @SwapRows@ and @SetRow@ were already available.
Now they are in the manual. -
- In CoCoALib we have some functions for Gaussian Elimination.
Choose which and how to make them available at CoCoA-5 ... -
-
- I slightly improved the menu so that it indicates which splitting is defined.
(with a tick next to side-by-side or t... -
- fixed. Now using @CopyHPPower@ (copies the precomputed value or computes the correct one) instead of @HPPowerList@ (...
-
- (sorry, I meant "101")
I found where the problem is (a hard limit = 100 in GlobalManager) and I am fixing it.
-
- I've just tried with my own "local" copy of C5; seems to work fine (even trying several times).
Platform is MacOSX 1... -
- ...
28 Jun 2014
-
- 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
-
- I tried the newest cvs version and CoCoALib does compile in 32 and 64 bit. I only had to change what I have reported ...
-
- If there were any serious problems, they'd have come to light by now (almost 24 hours of testing!)
Closing.
-
- > All in all, it really does seem to be a "useless" feature...
and was not in CoCoA-4. It's a pointless exception.
-
- Here is a possible reason for wanting to allow juxtaposition of strings: if an input includes a very long string lite...
-
- How will rings be printed in resolutions?
I recall that CoCoA used a syntax like @ring#7@; we could do this (but i... -
- This bug essentially vanished when we abolished multiline string literals.
Now that juxtaposed strings literals ar... -
- I have (temporarily?) disabled recognition of juxtaposed strings. The resulting behaviour on the example input is:
... -
- OK for a menu flag which indicates the preferred way of splitting.
Some while ago I added to @cocoa5.el@ the fn @c... -
- Apparently (on Aquamacs) it splits horizontally or vertically depending on the width of the window. That may be conf...
-
- Almost all done. still missing: gui on windows
25 Jun 2014
-
- I tried; it compiled and all tests pass. Will test more tomorrow, and then check in.
-
- I believe the relevant source is in @Parser.C@ lines 2095-2103 inclusive.
I'll try commenting out, and see if everyt... -
- > Can we remove this "feature? What was the original reason for wanting this?
The original reason was to allow it ... -
- Currently CoCoA-5 accepts juxtaposed string literals (_i.e._ separated by nothing or white space).
Can we remove t... -
- I have modified @cocoa5.el@ to add escapes for @"@ and newlines inside filenames.
A quick test showed that it works a... -
- The name @RingWithID@ is longer than I would like; I originally suggested @ring(3)@ but that is not so clear. Maybe ...
-
- If we go with the idea of printing simply @RingWithID(...)@ then I presume the @describe@ command should fully descri...
-
- If I recall correctly, we abolished "superstrings" in CoCoA-5.1. So the problem is no longer relevant. In any case,...
-
- I have now added a new test, @test-RingElem4@, for @CmpAbs@ of @RingElem@. Will check in.
24 Jun 2014
-
- Here is an excerpt from CoCoA (this morning, 20140624)...
23 Jun 2014
-
- Christof is still trying to make @cmake@ behave well on MacOS; both static and dynamic libraries give (different) pro...
-
- The symbolic link approach now seems to be working -- I even tried with a nasty directory name apparently without mis...
20 Jun 2014
-
- John Abbott wrote:
> *Bad* it is not clear how to specify a custom "installation" of GMP instead of the standard sys... -
- Christof has been investigating using @cmake@ for configuring normaliz/libnormaliz.
*Good* @cmake@ seems to handle... -
- The @cmake@ program offers a platform independent "configuration" mechanism. In principle it could replace CoCoA's e...
19 Jun 2014
-
- I thought I could be clever in @autoconf.mk@ and use @-lgsl@, @-lfrobby@ and so on.
*But* the linker does some strang... -
- Here's a quite summary of the current situation (created entirely manually so far).
There's a new directory @configu... -
- John Abbott wrote:
> I now think that the correct place for the external library directory is in @configuration/@.
... -
- I now think that the correct place for the external library directory is in @configuration/@.
It may as well be ca... -
- 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
-
- To avoid problems with "awkward" path names to external libraries, I suggest creating symbolic links (with nice names...
14 Jun 2014
-
- All done. It is also easier now to change which chars are allowed as 1st of symbol head, and which are allowed after...
-
- Implemented & documented; no test yet.
Checked in by commenting out the other changes in @ring.C@
-
- I have added a test and doc for @CmpAbs@ for @BigRat@
-
- I have now checked in an impl for @BigRat@.
I have an impl for @RingElem@ but cannot yet check in (mixed up with oth... -
- I was unable to add a @JBMill@ field to a SparsePolyRingIdeal because of circular includes.
One solution would be ...
13 Jun 2014
-
- John Abbott wrote:
> It would be handy to have a ctor for @RingElem@ which accepts a @RingBase*@ instead of a @ring@;...
12 Jun 2014
-
- Everything compiles & all tests pass :-)
It would be handy to have a ctor for @RingElem@ which accepts a @RingBase... -
- Make sense.
We should also do the same (when someone asks ;-) for other functions which can be extended from BigInt ... -
- The current impl works only for int/BigInt. Not for @BigRat@
-
- We have the fn @CmpAbs@ for @BigInt@ and @BigRat@.
Mario would like it also for @RingElem@ (when it is an ordered do... -
- John Abbott wrote:
> which ring functions should be extended in this way?
I see this question in other terms: whi... -
- Mario Albert said it would help make code shorter (and more readable) if one could write @PPM(f)@ instead of @PPM(own...
11 Jun 2014
-
- I have managed to remove most of the need for @AsPolyRing@; will continue later this evening.
-
- The documentation for @ReductionCog@ need to be improved (and corrected?)
-
- John Abbott wrote:
> If we allow a wider range of heads, I suggest that any head may be indexed (rather than trying ...
Also available in: Atom