#507 closed proposed feature (wontfix)
including other files in a LIB package
Reported by: | Owned by: | somebody | |
---|---|---|---|
Priority: | minor | Milestone: | 3-2-0 and higher |
Component: | dontKnow | Version: | 3-1-6 |
Keywords: | Cc: |
Description
Hello,
is it possible to include code from other files in a Singular .lib file, that means, separate a package into a couple of files?
I asked this question in the forum, but did not get an answer. This feature will help to organize a library into smaller logically grouped peaces.
If this is not desired or unfortunate, please give some arguments.
Thanks
Jakob
Change History (4)
comment:1 Changed 10 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 follow-up: 4 Changed 10 years ago by
You can use static procs from other libs in your procedures (!) by specifying the package name, e.g.
listvar (Standard); // Standard [0] package Standard (S,standard.lib) ... // ::intersect1 [0] proc from standard.lib (static) ... proc my_intersect1(a,b) { return ( Standard::intersect1(a,b) ); };
comment:3 Changed 10 years ago by
ok
just for completenes ( it was probably discussed several times before):
what are the main reasons for 'wontfix' of this issue?
Thanks,
Jakob
comment:4 Changed 10 years ago by
Hi ,
thanks for the hint for accessing static procs from other procedures.
Replying to motsak:
You can use static procs from other libs in your procedures (!) by specifying the package name, e.g.
listvar (Standard); // Standard [0] package Standard (S,standard.lib) ... // ::intersect1 [0] proc from standard.lib (static) ... proc my_intersect1(a,b) { return ( Standard::intersect1(a,b) ); };
Each library creates its own name space - no access to internal routines from other libraries. Access to the public routines from other libraries is possible: simply list the required libraries in the header.