Design #1477
Updated by John Abbott almost 4 years ago
Bernhard Andraschko asks:
* *(A)* *@?package@* yields the manual for *@export@*. This is probably not intended.
* *(B)*
The manual for packages contains the *@See also: ? CoCoA Packages@*, but *@? CoCoA Packages@* doesn't provide any result.
* *(C)*
If I write a package, i must export one of the functions. Why do I have to do that?
Maybe I just want to write a package @$sthg@ and then access all functions in it by calling @$sthg.foo()@
* *(D)*
Required packages. Originally I had one package *@$subalgebra@* and another called *@$sagbi@* and both of them required the other one to work, but i can't put @source $otherOne@ in both files since then they would "load itself" recursively. Also *@IsDefined($subalgebra)@* gives an error, maybe there is a different syntax producing what I want. Something similar to @#ifndef@ in C++ would be useful in CoCoA?
* *(E)*
Documentations. Is there any way to access package documentations without looking in the source code? I only see the function *@describe@* which gives me all functions in a package, but e.g. there is a package *@$sppoly@* and I have no idea what it does (and no idea how to find out).
* *(A)* *@?package@* yields the manual for *@export@*. This is probably not intended.
* *(B)*
The manual for packages contains the *@See also: ? CoCoA Packages@*, but *@? CoCoA Packages@* doesn't provide any result.
* *(C)*
If I write a package, i must export one of the functions. Why do I have to do that?
Maybe I just want to write a package @$sthg@ and then access all functions in it by calling @$sthg.foo()@
* *(D)*
Required packages. Originally I had one package *@$subalgebra@* and another called *@$sagbi@* and both of them required the other one to work, but i can't put @source $otherOne@ in both files since then they would "load itself" recursively. Also *@IsDefined($subalgebra)@* gives an error, maybe there is a different syntax producing what I want. Something similar to @#ifndef@ in C++ would be useful in CoCoA?
* *(E)*
Documentations. Is there any way to access package documentations without looking in the source code? I only see the function *@describe@* which gives me all functions in a package, but e.g. there is a package *@$sppoly@* and I have no idea what it does (and no idea how to find out).