People,

Why can't we all get along???

Sometimes subroutines make sense. As Duane pointed out, sometimes it's
more hassle to pass a long list of global variables into a subprocedure
than it is to simply use a subroutine.

For instance, I have a precompiler program which has a recursive
procedure to process several different source members. Given that the
first thing I want to do is to read the entire source member into an
array (local to the subroutine) it's much easier to do this as a
subroutine. If I implemented the file-read as its own procedure, I'd
still need to pass the array into/outof that procedure anyway.

Given that finally I need to copy the local array into a global array,
(so I'm using a subroutine inside a procedure, both of which access
local variables and global variables) I'm worried that someone here is
going to shoot me for my 'bad' coding practices...

Rory

p.s. I didn't even get into the use of procedure-specific *PSSR
subroutines. I have one in every procedure I have, so I guess I'm just
used to having subroutines and procedures working together.


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.