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



> From: Buck Calabro
>
> Once more, foot into my mouth!  For what it's worth, in my opinion, using
> subprocedures this way is not a good way to design an application.  I
> believe the intended use of subprocedures is to do ONE SIMPLE thing, and
> that it should know NOTHING about global variables.  Some think
> me Utopian,
> but why make a subprocedure if the guts are basically a complete
> program?  I
> mean, why not just leave it as a program?

I think this depends on what the program does.  If the files are closely
related and the program is doing a single business function (updating a
customer order, for example), then I think this is perfectly fine.

In the most perfect of worlds, I'd rather see one and only one module access
any given file, and that module be called by everyone else.  Each module
would access only a single file or a set of file with direct parent/child
relationships, such as order header and order detail.  If one program than
had to access another file, it would do it through a call to that file's I/O
module.

Joe


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.