× 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.



Rob,

There's not much you can do with people that use SEU _and_ don't like
/INCLUDE or /COPY. I think this is mostly due to the fact that they can't
"see" the variables or prototypes in SEU.

When I use SEU, I prefer to see a /COPY or /INCLUDE because I know that
there is code in there that I can use, but I don't have to see it and have
it clutter up the editing session. But then again, I rarely use SEU much.

-Bob



On 8/8/06 7:31 AM, "rob@xxxxxxxxx" <rob@xxxxxxxxx> wrote:

I'm not much into those kind of absolutes Steve.  It is not uncommon for
me to have in my main program
      /INCLUDE ROUTINES/QAPISRC,ERRC0100
      /INCLUDE ROUTINES/QAPISRC,SOMEAPI
and that SOMEAPI might have
      /INCLUDE ROUTINES/QAPISRC,ERRC0100
in it also.  So it would bomb if I didn't have conditional compilation
because it would be defined twice.
Now, I tried the huge monolithic SRVPGMCPY source that would have all
possible combinations of APIs, datastructures, commonly used constants,
etc.  But I ended breaking it up.  Primarily because I was under the
mistaken belief that I was being told the truth from some of the more anal
people I work with that they wouldn't use that because they didn't like to
define variables that they didn't use because of memory constraints, etc.
However, even after breaking it up they still use Sucky Edit Utility to
manually copy in the lines from the INCLUDE module and dink with it by
changing some of the variable names, etc.

Rob Berendt



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.