Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!uxc!uxc.cso.uiuc.edu!ux1.cso.uiuc.edu!uicsrd.csrd.uiuc.edu!jaxon
From: jaxon@uicsrd.csrd.uiuc.edu
Newsgroups: comp.lang.apl
Subject: Re: Problem with )COPY
Message-ID: <49700009@uicsrd.csrd.uiuc.edu>
Date: 21 Apr 89 16:04:00 GMT
References: <575@moore.UUCP>
Lines: 9
Nf-ID: #R:moore.UUCP:575:uicsrd.csrd.uiuc.edu:49700009:000:418
Nf-From: uicsrd.csrd.uiuc.edu!jaxon    Apr 21 11:04:00 1989


The only cleaning-up that such a procedure does is to remove the )SI state,
(You could )RESET), and to give all system variables their default values.

"Heavy use" of a library workspace only affects it when you )SAVE.

)COPY is THE most complex system command to implement (P.S., I claim to
have the fastest version for nested-array WSs)  Perhaps IPSA is "cleaning-up"
on CPU and I/O billings by encouraging its use.