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



Sorry if I came across as offended - I wasn't.

I understand the name collisions - this whole thread started with asking
why we put suffix characters on the end of our printer files; O, R, or
P1, etc.  The one source file approach is why I do that.

Bob Cagle
IT Manager
Lynk, Inc.
8241 Melrose Drive
Lenexa, KS  66214
913-492-9202 ext.41
mailto:bcagle@xxxxxxxxxxx


-----Original Message-----
From: Buck Calabro [mailto:Buck.Calabro@xxxxxxxxxxxx] 
Sent: Wednesday, March 26, 2003 3:38 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Naming conventions - was ->RE: Replacing *entry plist

>I know it is really a personal preference, but give me 
>one really solid reason why you shouldn't combine source 
>members this way?  

Knowing Booth, he was pulling your leg, and it just didn't come across
that
way in writing.  But I can give you a reasonable reason for multiple
source
files: name collisions.  As you say, it is a company/personal standard.
  --buck
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.