Activity
From 03 Sep 2020 to 02 Oct 2020
02 Oct 2020
-
21:05 Design #1495: Package exporting nothing?
- Prototype still needs to be cleaned... not today!
-
- Here are the tests we should make:
* *(1)* package with no @export@ commands (warning, as now)
* *(2)* package w... -
- I have written a first prototype. It compiles and seems to do the right thing, but I must do some more testing.
The... -
11:31 Design #1495 (In Progress): Package exporting nothing?
- From #1477 point (C)
proposed syntax *@export skip;@* -
- It may be useful to make a package exporting no function: currently it gives a warning.
Choose an explicit syntax ... -
- It seems that the root cause was in @LexemeClass@... which was poorly written (by me?).
I have rewritten it, and all... -
- Here is a list of the tests: we can remove the ones which have been checked/updated....
-
- *COPIED FROM COMMENT 3 in #1294*
One possibility is simply to use names which start with underscore: this is allow... -
- To avoid problems with name clashes the names of variables inside test scripts these variable should have "special" n...
-
- John Abbott wrote:
> Any news about this package?
> Can we close this issue quickly and easily?
ok, working on i... -
- After a Skype discussion we have decided to leave things as they are: while not perfect (and sometimes annoying) the ...
-
- John Abbott wrote:
> Is this even a bug?
> In my installation the symbol *@Gens_Ker_Mod_Hom@* is indeed exported by... -
- John Abbott wrote:
> My "gut feeling" is that it should work... I expect it to work (perhaps because the destination... -
- John Abbott wrote:
> Regarding point *(C)* _why must a package export at least 1 function?_
> We could also allow s...
30 Sep 2020
-
- It looks like the error mesg was generated by @Parser.H:159@.
There is also a comment in the code referring to #673.... -
- My "gut feeling" is that it should work... I expect it to work (perhaps because the destination ring is well defined?...
-
- Regarding point *(C)* _why must a package export at least 1 function?_
A work-around would be to create a function...
28 Sep 2020
-
- We have partly implemented automatic conversion of ring elements (_e.g._ in multiplication).
Should it also work for... -
- I suspect that the relevant part to be changed is the defn of *@cocoa5-beg-block-re@* around line 286 in @cocoa5.el@....
23 Sep 2020
-
- Is this even a bug?
In my installation the symbol *@Gens_Ker_Mod_Hom@* is indeed exported by a package called *@expe... -
- The relevant line appears to be *@Interpreter.C:4289@*.
Here is a test input which triggers the bug:... -
- I am postponing this because it is not so important/urgent, and looks like it might be quick tricky to solve :-/
-
- I think I now prefer not to issue a warning in the examples given here.
If CoCoA issues too many warnings then the u... -
- I have implemented option *(A)* and checked it in. I chose *(A)* because it is relatively simple to implement.
Wait...
17 Sep 2020
-
- The following produces a misleading error message...
-
- Any news about this package?
Can we close this issue quickly and easily? -
- I have modified the script @RunTests.sh@ so that it first runs CoCoA with an empty input (*@/dev/null@*).
If that pr...
15 Sep 2020
-
- Your comment about a protected variable causing trouble is a good point (albeit also rather abstruse).
We should u... -
14:35 Bug #1294: CoCoA-5 tests may fail even if executed correctly
- Yes, I think that would be an improvement, but also only solve the issue partly. Still if for instance @init.cocoa5@ ...
-
- To read a local file one needs to open an input device via @D:=OpenIFile("path_to_file")@ and read it line-by-line vi...
14 Sep 2020
-
- JAA is uncertain about this.
On the one hand the "strange" indentation of package variable assignments highlights ... -
- Bernhard Andraschko reports the following anomaly.
Inside a package variables are indented, but all other package ...
Also available in: Atom