> > main-program change and I then re-compile the sub,
> then the other
> > main-program (which depends on the sub) could get
> whacked.
It is more of a pain to maintain programs that depend
on a shared include than maintaing a common
subroutine.
One way to limit the impact is to plan for new
parameters being passed to your subroutine. You can
have an unused DIM Matrix of a certain size (like 20
or so).
If you need later on to pass opened files or other
variables, you can simply use the unused fields in the
Matrix. Existing programs won't neccessarely need to
be modified as the number of parameters passed hasn't
changed.
You only need to take into account that the new
parameters may not have been filled out.
I've seen some dumb things in shared includes and/or
commons such as variables called X or I. These
values tend to get changed when someone needs a FOR loop.
Yahoo! Mail
Stay connected, organized, and protected. Take the tour:
http://tour.mail.yahoo.com/mailtour.html
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
