×
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.
On 4-Feb-08, at 1:38 PM, wdsci-l-request@xxxxxxxxxxxx wrote:
I find that my list of members in a source physical file growing
larger the
more I adopt modular practices. I would only expect them to grow
in number.
How would they be separated out differently? Logically separate
them into
differenlty named source physical files?
Well I got the impression that the OP had all source members for all
applications in a single file.
I agree that more modular practices increase the number of files, but
I tend to group relates subprocedures in a single source anyway.
Also I would associate a subsystem with a single file rather than a
whole system.
I should point out that I find large lists unmanageable in PDM as
well as in WDSC/RDi - so I'll use many techniques to avoid it.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
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.
midrange.com
