On Tue, 15 Jan 2019, Sven Schreiber wrote:
> Interesting. But I think what you're describing could be done
just in
> memory, without writing a temporary package file. The idea would be:
>
> 1) Load A.gfn as usual, detect deep-dependency on B.
> 2) Load B.gfn in a (new) "merge mode", whereby its public functions and
> added to A's public list and its private functions to A's private list. So
> package B is not really loaded as such, its content is just merged into
> that of A on the fly.
>
> A.gfn and B.gfn on disk would not be affected.
If that's easy internally, it sounds quite nice, yes.
I've marked the relevant GUI string for translation. I believe we should
update the packages tex file on this, which is quite important.
A question (no time to check myself, sorry). If A has B as a sibling and B
has C, is C a sibling to A?
-------------------------------------------------------
Riccardo (Jack) Lucchetti
Dipartimento di Scienze Economiche e Sociali (DiSES)
Università Politecnica delle Marche
(formerly known as Università di Ancona)
r.lucchetti(a)univpm.it
http://www2.econ.univpm.it/servizi/hpp/lucchetti
-------------------------------------------------------