|
Barbara, Please correct me if I misunderstand this... > Joel Cochran wrote: > > > > And to add to the fine points already listed, using procedures > > verifies your program calls at compile time rather than run time. > > An easy way to prevent parameter mismatches. > > Joel, that's a benefit of prototypes, not of procedures. You can make > a prototyped call to a program. > I can always prototype the program call incorrectly. The compiler will ensure that I call the way that I have prototyped, but not necessarily the way the *Entry PLIST was defined. I do not get that kind of checking unless I use Sub-Procedures and a /COPY book to check the prototype against the interface as I compile the module. Andy
As an Amazon Associate we earn from qualifying purchases.
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.