× 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: Single vs. Multiple Source Files (was Size of source physical files)
  • From: "Njål Fisketjøn" <n.f@xxxxxxx>
  • Date: Wed, 25 Jul 2001 21:27:46 +0200
  • Importance: Normal



> -----Original Message-----
> From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
> Behalf Of Joel Fritz
> Sent: 25. juli 2001 20:45
> To: 'RPG400-L@midrange.com'
> Subject: RE: Single vs. Multiple Source Files (was Size of source
> physical files)
> 
> 
> That's something I've been thinking about recently.  With the new
> opportunities for modularization that ILE offers, one source file per
> project, or project subgroup, makes a lot of sense.  
> 

I think that would make it harder to "navigate" and find what you're after
if you're not *very* familiar with the system.

If only IBM would let us use IFS for all source (ie let all compilers support 
it),
I could be tempted to try. IMO there's still advantages to having a relatively 
flat
source hierarchy.


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

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.