I haven't tested yet, but your description sounds perfectly workable to me.
Thanks!
Blake
Sent via the Samsung Galaxy Note® 4, an AT&T 4G LTE smartphone
-------- Original message --------
From: Juergen Sauermann <[email protected]>
Date: 2/8/2016 8:32 AM (GMT-06:00)
To: Blake McBride <[email protected]>, [email protected]
Subject: Re: [Bug-apl] Copy of dumped WS copies everything
Hi Blake,
thanks, sort of fixed in SVN 694. It may not work
properly, though, if a file
was not )DUMPed or modified manually after )DUMPing
it. Reason: DUMP
files contain APL code that is being executed. Therefore it is in
general not
decidable if that code may create a particular function or
variable.
/// Jürgen
On 02/07/2016 11:45 AM, Blake McBride
wrote:
)CLEAR
CLEAR WS
∇F1
[1] ∇
)DUMP WS1
2016-02-07 04:32:05
(GMT-6)
)CLEAR
CLEAR WS
∇F2
[1] ∇
∇F3
[1] ∇
)FNS
F2 F3
)DUMP WS2
2016-02-07 04:32:42
(GMT-6)
)LOAD WS1
DUMPED 2016-02-07
04:32:05 (GMT-6)
)FNS
F1
)COPY WS2 F2
DUMPED 2016-02-07
04:32:42 (GMT-6)
)FNS
F1 F2 F3
F3 should not be there.
Of course the copy works with workspaces but has this error
with dumped workspaces.
I feel as though I am being pushed to use dump files rather
than workspaces because of the fact that dumped workspaces
better survive GNU APL upgrades. (I got caught on that one
with a WS I hadn't used in a while.) Not being able to store
the SI on dumped files is unimportant to me because the SI
doesn't matter on a WS you hadn't loaded in a year and a
half. The saved SI is mainly good for WS's being actively
debugged. But - the ability to copy functions is used on old
WS's.
It would be handy to have )COPY work on dumped workspaces.
Thanks.
Blake McBride
