RE: QRPGSRC vs. QRPGLESRC -- MIDRANGE-L

× 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: QRPGSRC vs. QRPGLESRC
From: "Tucker Gerry" <Gerry.Tucker@xxxxxxxxxxxxxxx>
Date: Tue, 21 Jan 2003 16:25:28 -0000
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo.cgi/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo.cgi/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>
Thread-index: AcLBaR2Ov7oEKS1aEde2ygBQi7kIjQAAcSyw
Thread-topic: QRPGSRC vs. QRPGLESRC

I only have one source file, record length of 112, for ALL member types.  All 
source members are unique because of my object naming standards.

There is no hard and fast rule and the compilers don't mind either way.

Regards,
 
Gerry Tucker
Senior Analyst Programmer
Technicolor Distribution Services
Wembley, U.K.

"All my life I wanted to be somebody.
Now I see that I should have been more specific."

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.