Re: Protecting binary libraries in VAX Ada

[arny@wayback.UUCP (Arny B. Engelson)]

In article <8802291335.AA14051@ajpo.sei.cmu.edu>, mooremj@EGLIN-VAX.ARPA ("MARTIN J. MOORE") writes:
> > From: clyde!wayback!arny@bellcore.bellcore.com  (Arny B. Engelson)
> > [...]  My (current) solution (using DEC's VAX Ada) is to simply delete the
> > .ADC (the copied source) files from the Ada library for those units that 
> > the user doesn't need to see.  [...] 
 
> You are working too hard.  You can tell the VAX Ada compiler not to create
> the .ADC files in the first place by using the /NOCOPY_SOURCE qualifier on
> the ADA, ACS COMPILE, or ACS RECOMPILE commands.  From the on-line help text:
 
[Manual entry deleted for brevity]

Yes, I know all that.  Problem is, the copy of the library I am sending out is
the same version my in-house users are using.  *I* need the source code there
so I can use the symbolic debugger when a problem is found, and know I am using
it on the same version of the program(s).  So, I temporarily copy the .ADC
files to another directory, make the tape, and copy them back.  Soon, I will
be able to separate the development and released versions onto different disks,
which will enable me to build a separate library for release and to reload old
releases without affecting the development version.

Even so, typing in 2 "rename" commands is not all that much work.  And if this
were the most worrisome problem in sending contract deliverables, I would cry
tears of joy.  SInce this is a fairly limited topic, I suggest any further
comments on this be mailed direct.

Arny Engelson
{ihnp4,clyde}!wayback!arny