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


  • Subject: Re: how to let my program sleep a while
  • From: booth@xxxxxxxxxxxx
  • Date: Wed, 20 Sep 2000 13:54:23 GMT

ok, this is the place I usually start getting lost when trying to maintain 
this new stuff.  What are you doing, and what is the advantage?  Are these 
added lines of code just to prevent having to define a field as *HMS in a 
prototype?
_______________________
Booth Martin
Booth@MartinVT.com
http://www.MartinVT.com
_______________________




Jon.Paris@hal.it
Sent by: owner-rpg400-l@midrange.com
09/19/2000 03:20 PM
Please respond to RPG400-L

 
        To:     RPG400-L@midrange.com
        cc: 
        Subject:        Re: how to let my program sleep a while


 >> If it were me writing this, I would use the /COPY member and declare
and constants in that.  Perhaps put most of my constants in one file.

Since RPG IV now supports both nested /COPY and conditional compilation
directives, you can combine these to good effect for handling constants.

Put all constants (or at least the set you want) into a single source
member.  Put the following (or similar) at the beginning of the source
member.

 /If Defined(sourcemembername)
 /EOF
 /EndIf

 /Define(sourcemembername)

 * Actual copy member content starts here.

This avoids the possibility of copying the file twice if it is referenced
from multiple prototype copy members.

I have also seen conditional compilation directives used to selectively
copy parts of a set of prototypes or constants.  In this case the proto
sets an appropriate condition name prior to issuing the /COPY.  The source
containing the constants uses conditioning to ensure that constants
required are copied once and once only.

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: 
david@midrange.com
+---




+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.