|
Hi, We use a 3-library system: one for sources, one for objects and one for data. Considering that the sources and objects in a production environment normally don't change, we only do a *changed backup of these libraries, whereas the data library is saved completely every day. About the sources, I can give you the standard reply: _it depends_. If you have an application with hundreds of objects, files and programs, it tends to get complicated if everything is in one single source file. Plus you can't have duplicate names for members. Just my opinion of course. HTH, Peter Colpaert Application Developer Honda Europe NV Langerbruggestraat 104 B-9000 GENT Belgium Peter.Colpaert@honda-eu.com Tel: +32 9 2501 334 Fax: +32 9 2501 231 ---------- Yoda of Borg are we: Futile is resistance. Assimilate you, we will. ---------- "Rusty Luse" <rluse@cronus.cc>@midrange.com on 03/10/2002 16:14:51 Please respond to midrange-l@midrange.com Sent by: midrange-l-admin@midrange.com To: <midrange-l@midrange.com> cc: Subject: Library and Source File Question 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 _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. ______________________________________________________________________ The information contained in this communication is confidential and may be legally privileged. It is intended solely for the use of the individual or the entity to whom it is addressed and others authorised to receive it. If you have received it by mistake, please let the sender know by e-mail reply and delete it from your system. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance of the contents of this information is strictly prohibited and may be unlawful. Honda Europe NV is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.