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



I am in the process of setting up some standards for creating libraries,
source files, objects, etc.  I have two questions that I would appreciate
some help with.

1.  Is there a major pitfall that I may encounter if I choose to setup a
library that will contain all objects for a particular application?
     This library would include all program objects and data files.  Should
I separate my data files into another "data" library?  Half of my
     coworkers think we should separate the data and objects while half
think it is easier to keep everything in one library.  What are the
     advantages and disadvantages?

2.  This question is similar to the first question except it deals with
source files.  Many of my coworkers believe that we should keep all
     of our source in one source file instead of separating them by QDDSSRC,
QCLSRC, QRPGLESRC, etc.  I prefer to separate my
     source but am not against changing if one source file is better.  Any
suggestions?


Thanks,
Rusty



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.