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



On Wed, 13 Aug 2003, Joe Pluta wrote:
>
> So perhaps the idea is to use the MODULE name as the prefix.  That way,
> I'd never have conflicts.
>
> What do you think?
>


This is similar to what I do.   Each service program has a prefix, and
anything that's exported or in the /copy file starts with that prefix to
avoid conflicts.

So, for example, if I have a service program for Finished Goods Inventory
routines, I prefix everything with "FGI_".   FGI_findpallet(),
FGI_adjustcount(), as well as constants:  FGI_OK, FGI_NOTFOUND, etc, and
"typedefs" (fields defined solely for the use of LIKE on D-spec) will work
the way that you suggest, by bringing in an external DS, and using
PREFIX(FGI_)

Then, of course, I use /if defined() and /define to make sure that my
/copy file isn't brought into my program more than once.   That way, if
the "Order Picking" service program needs definitions from the FGI service
program, it can bring in the FGI /copy file without worrying about a
conflict if some program wants to use both PICK and FGI.   (I hope this
paragraph makes sense.)



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.