Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!wam.UMD.EDU!stripes
From: stripes@wam.UMD.EDU
Newsgroups: comp.lang.apl
Subject: Re: Problem with )COPY
Message-ID: <8904260118.AA00268@vs08csc.UMD.EDU>
Date: 26 Apr 89 01:18:15 GMT
References: <575@moore.UUCP>
Organization: (not much)
Lines: 66

In article <575@moore.UUCP> paul@moore.UUCP (Paul Maclauchlan) writes:
>
>When trying to clean up a heavily used workspace on the system
>we attempted to create a new "clean" version by:

Does "clean" mean "no extranious globals", or internal junk?

>2. )SYMB 3000, to match the symbol table size in the old ws

I'm not shure what version of APL*PLUS/Unx you are running, but current
versions have a dynamic symbol table, the (but I think it only grows,
you have to shrink it yourself, and if you are adding ALOT of syms it's
faster [by a tad] to )SYMB the size yourself).

>1. Why does setting the symbol table size affect the )COPY command?

The author of the code (my Dad) was perplexed by this; the code has been
since re-written, I don't think the bug exists on new systems.
His only idea was that you re-sized the sym. table that somehow the
label bit remained set...

>	1a. Shouldn't matching the symbol table size to that of
>	    the original workspace be the "right thing" to do?

Not if the system will re-size on the fly for you.

>2. Are the )COPY and QuadCOPY commands reliable?

Yes, but they are not a placenta for real "WS DAMAGE" (sym table
damage).

>	3a. Does it make a difference in system performance to
>	    have a "clean" workspace?

Yes, you lose some.  Copy does not copy the P-code, so on the first execution
of each line it must be re-created.

>	3b. Does it make a difference in performance to use a
>	    workspace saved with a value assigned to QuadDM?

It shouldn't.

>	3c. How are we supposed to fix a "damaged" workspace?

Copy is the best method short of a disk editor and system level documation
(never created, let alone distributed).  As stated before it's not
fool-proof.
You should also try "Quad-VR Each Quad-NL 3 Quad-FAPPEND tie-number"
(each is shift-1, I think), ")CLEAR", and "Quad-DEF Each Quad-READ Each
tie-number,Each Iota #of-comps".

>Any help we can get answering these questions will be appreciated.

You are welcome, but let it be known that I am not an expert, I have never
seen most of the code.

>Technical notes:
>Some background, we are running STSC APL*PLUS/UNX 3.1.1 for the
>Spectrix computer, under SCO XENIX Version 3.1.

Hate to tell you this version is no longer supported, nor is the
Spectrix computer.
-- 
           stripes@wam.umd.edu             Disclamer:
      Josh_Osborne@Real_World,The           I no longer work for STSC, but my
      "Just another dyslexic porgramer"     Dad does....