Am 15.01.2019 um 17:48 schrieb Allin Cottrell:
On Tue, 15 Jan 2019, Sven Schreiber wrote:
> Am 05.12.2018 um 15:56 schrieb Sven Schreiber:
>> Am 05.12.2018 um 15:54 schrieb Allin Cottrell:
>>> On Wed, 5 Dec 2018, Sven Schreiber wrote:
>>>
>>>>
>>>> One step further in this experiment: It seems that when A depends
>>>> on B, the private functions of package B are still _not_ available
>>>> in package A. (Right?) This is not too surprising, but in my case
>>>> creates a problem.
>
> Hi, when I wrote the other message on the users list about the SVECM
> GUI right now I had another idea:
>
> What if something like a "deep dependence" between packages is
> introduced
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.
thanks,
sven