×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
<snip>
I'm very familiar with that; I've been using a variant of that concept
for a long time now, but only for those 'funny' sorts of compiles where
PDM option 14 won't do it.
The reason to capture the compile commands is so I can re-create all the
related objects in my test library during testing, but mostly so I can
recreate them all once the source gets moved back to production. The
problem isn't the compilation, so much as identifying the members to be
compiled.
</snip>
Buck, if you used my Compile command, couldn't you just create a simple
command to capture what you are compiling into a table and then just
loop through the table issuing Compile on each object?
The instructions in the header can be any interactive command.
It is probably more complicated than that. I don't know if you are
trying to capture by a project or something.
Maybe you could just set a data area or something with the current
project and capture all the compiles by that project or whatever.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
