Activity
From 05 Jun 2012 to 04 Jul 2012
04 Jul 2012
-
14:44 Feature #193: BuiltinFunctions.C getting too long (2000 lines)
- Should we also separate builtin function from external libs? (I think so)
if so, should we have
*BuiltinFunctionsNo... -
- Proposal for most powerful/flexible function to access *Normaliz* capabilities
(specific functions like *NormalizHil... -
-
09:50 Bug #98 (Closed): RealRoots should use IsRational
- No further problems have surfaced, so closing the issue.
-
- Also *First([])* and *Last([])* were buggy: fixed
-
- The problem is in the function *First(L,N)* when N is larger than the length of L.
Fixed.
03 Jul 2012
-
- Whatever the user error is, CoCoA should never crash. Investigate....
29 Jun 2012
-
- We have modules in CoCoALib.
Just mimick ideals to add modules..... will it be that easy?
Probably we'll have som... -
- Problem for the GUI release:
even though it works reasonably well, there is a bug related to the fact that (by defau... -
- Per chiarirci le idee prima di spargere la voce...
*relatore Informatica*: Giovanni Lagorio? Paola Magillo?
*ge...
28 Jun 2012
-
- added to script generation of pre-release for cocoa-5.0.3 for Mac emacs
(and made pre-release)
26 Jun 2012
-
- John Abbott wrote:
> Will we use the banner in the GUI?
I think it is nice to have something looking like "I'm re... -
- I placed the definition of the banner in the files *Banner.[CH]*.
I do not like adding a separate file for such a sm... -
- I have the first "complete" version of *cocoa5-cvs-snapshot*.
* It assumes the cvs copy in my "0.99/snapshot" directo... -
- I've found this bug (among the other "surprise" and rare occurrences) is caused by *make; make;* which seemed to occ...
-
- Sometimes we get this mysterious message when starting the GUI....
25 Jun 2012
-
- I've created on my computer a "snapshot" directory for the "current cvs snapshot" where I should compile (and also ge...
22 Jun 2012
-
- Another problem...
21 Jun 2012
-
- John Abbott wrote:
> No idea why it was so slow before :-(
I had a similar problem to what you described yesteray... -
- I think this latest proposal is a good start. It contains the most useful information, and the names of the fields a...
-
- ...
-
- I suggest removing the @CoCoA@ prefix from the compilation date, the compiler name, and the compilation options.
I... -
- see above
-
- I changed the relevant lines (near 2910) in @Interpreter.C@:...
-
- CoCoALib produces a "mixed rings" error in the following example; CoCoA-5 does not intercept the error at the level o...
-
12:39 Feature #193: BuiltinFunctions.C getting too long (2000 lines)
> I think we have to make two variables *@vector<NameFunPair> builtIns;@*
You can probably keep a single variabl...-
- One proposal for splitting is
- file A: general macros and templates
- file B: all oneliners (the easy ones) with... -
- Can we split BuiltinFunctions.C so that it is easier to update and faster to compile?
20 Jun 2012
-
- I did @make veryclean@; sync with CVS, and @make@.
Now mine takes about a minute too... very odd!
No idea why it ... -
- John Abbott wrote:
> The following example comes from an exercise I gave during _Algebra Computazionale_
> [...]
>... -
- Compare these...
-
- How to get the (string) values out of *BuildInfo.C* ?
At the moment there is...
19 Jun 2012
-
- The following example comes from an exercise I gave during _Algebra Computazionale_...
-
- added VersionInfo.
fixed documentation.
This could also return the other info in BuildInfo (such as compilation f... -
- I have added "division by a scalar" for matrices and lists; not added anything to the documentation, nor any example/...
-
- Claudia reports that @Matlab@ allows the user to write @M/2@ to mean @(1/2)*M@. JAA finds this reassuring because it...
-
- The function is called *PrintCoCoA5Banner*.
I'm checking it all in.
If by default it is printed badly in teh GUI we... -
- The cause of the problem is a design bug in CoCoALib (see issue #190).
As a consequence I shall close this issue.
... -
- If you add...
-
- @Valgrind@ even complains about the following two lines!!...
-
- According to *@valgrind@* the following input is enough to do damage:...
-
- I finally reduced the example: (quite a lot reduced ;-)
it seems due to having both a redefinition of the PolyRing a... -
- The problem appears to be a *@RingHomValue@* in the interpreter which has a reference to a CoCoALib *@RingHom@* which...
-
- Laura's code works fine on my Linux VM.
However, *@Valgrind@* confirms that there is a memory access problem (seems ...
18 Jun 2012
-
17:18 Feature #188: CoCoAManual: entries for operators
- John Abbott wrote:
> How would a student find out what @><@ means in CoCoA?
> How to have manual pages for operator... -
- Recompiled with MemPool debugging and linking with @debug_new.o@
The problem disappears... this may be enough to let... -
14:32 Bug #189 (Closed): malloc ERROR
- I get the following error...
-
- John Abbott wrote:
> @Anna: could you explain your preference for two separate functions rather than a single functi...
15 Jun 2012
-
- I have asked some students (and colleagues) about writing @M/2@ where @M@ is a matrix. The replies were quite varied...
-
- I believe the Linux kernel uses odd/even version numbers to distinguish between public releases and interim versions....
14 Jun 2012
-
- Added new test *@test-RingElem1@* which currently just does some simple sanity checks on @gcd@ and @lcm@.
Cleaned ... -
- Fixed the wrong result -- it was a bug in CoCoALib.
Fixed the type error (in @Builtin.C@) but fix is rather *ugly*.
... -
- How would a student find out what @><@ means in CoCoA?
How to have manual pages for operators in CoCoA?
Here is a... -
- @Anna: could you explain your preference for two separate functions rather than a single function?
JAA has a (mild...
13 Jun 2012
-
- I added a mechanism to make it simple to change the date in the manual.
So that *? CoCoAManVersion* prints the ver... -
- I added the functions *CoCoAVersion()* and *CoCoALibVersion()*.
Before I cvs it all in, how should the "version" fil... -
- It is reasonably easy now to make a new CoCoALib (snapshot) release.
On the other hand making a new CoCoA-5 is *quit...
12 Jun 2012
-
- ...
-
- John Abbott wrote:
> Should the field be called *@CoCoA5@* or just simply *@CoCoA@*?
> JAA prefers *@CoCoA@*. Its ... -
- John Abbott wrote:
> Common sense says that if you can do @M*(1/X)@ then you ought to be able to do @M/X@ (and get th... -
- John Abbott wrote:
> Should "5" be part of the banner?
I think so: it is quite different from CoCoA-4, so we'd be... -
- I agree to exclude @MATRIXROW@ and @RECORD@
> Can we create values of type @VECTOR@? Are they the same as @Module...
11 Jun 2012
-
- Scalar multiplication could be useful for:...
-
- Added scalar mult on the right & unary minus for matrices in C5.
-
- Added scalar multiplication on the right (for matrices) to CoCoALib.
-
- John Abbott wrote:
> I've just added *@operator-@* (scalar multiple by -1) to @MatrixArith@.
>
> Contrary to my s... -
- Common sense says that if you can do @M*(1/X)@ then you ought to be able to do @M/X@ (and get the same result!). If ...
-
- We can comupte INT*MAT, more recently also MAT*INT.
Should we also allow MAT/INT?
(was not allowed in CoCoA-4)
A... -
- Should "5" be part of the banner?
-
- Will we use the banner in the GUI?
It might be tricky to make it look good if/when the user changes font.
The pro... -
- I suggest this banner for CoCoA-5...
-
- Should the field be called *@CoCoA5@* or just simply *@CoCoA@*?
JAA prefers *@CoCoA@*. Its value will be a string... -
- John Abbott wrote:
> Strictly, each package should have its own version number (maybe they already do in the source ... -
- Strictly, each package should have its own version number (maybe they already do in the source text?) I'm not sure i...
-
- John Abbott wrote:
> I agree that the version number should be in the executable.
>
> If the version number is in... -
- Unary minus is implemented via a member fn -- JAA does not know why it was implemented in this way.
-
- In Interpreter.C there are templates for *opEqual*, *opStar*, ...
Can we have a similar template for *unaryMinus*?...
10 Jun 2012
-
- I've just added *@operator-@* (scalar multiple by -1) to @MatrixArith@.
Contrary to my suggestion that multiplicat... -
- John Abbott wrote:
> If *@N*X@* is valid (for @N@ integer, and @X@ of some type) then it makes perfect sense that @-... -
- *-M* is not available in CoCoALib whereas
@matrix operator-(ConstMatrixView Mleft, ConstMatrixView Mright)@
is.
Sh...
08 Jun 2012
-
- I have improved the warning message when the default package directory is not accessible (for text UI, and GUI).
T... -
- The parser goes into a strange state if an unescaped double quote character is found inside a superstring. It correc...
-
- Anna Maria Bigatti wrote:
> * disadvantages: I think the version number should be in the executable
> * advantage... -
- Something we had talked about:
cocoa-4 used to load the file *init.coc*.
I've found a _tappullo_: call this file *... -
-
-
- * revived the old code and removed (for the moment) the inclusion of the horribly obsolete chapters/sections/tutorial...
-
- added *apply*, *wdeg*, *PolyAlgebraHom*
removed *WeightsList* -
- we should make a catalogue of cases where we choose (for safety of the user) to throw an error even though there is a...
07 Jun 2012
-
- Here are a couple of suggestions which do not require manipulating @symbol@ directly. If these two fns cover almost ...
-
- Can I set the assignee to Anna Bigatti? :-)
Well, anyone so long as it is not me :-) -
- Added manual for *NewPolyRing*, *GradingDim*, *RealoadMan* (not yet cvs-ed)
-
- Anna's point about almost everything (eventually) being built-in is valid; I was forgetting that. Also my "note" in ...
-
- Make makefile target for *texdoc*.
Check that it is created nicely (quotes, dollars, ...)
-
-
- In adding the target to the makefile I cleaned up the manual related targets.
I'm not sure if I did it 100% right (i...
Also available in: Atom