|
This is just as true of subprocedures as it is of programs. If you try to use a parameter that was not passed, you get an error. That's only logical. In both cases, both programs and subprocedures that is, you can use %parms to see how many parameters were passed, and not use the parameters that were not passed. On Mon, 18 Nov 2002, Bartell, Aaron L. (TC) wrote: > I am right. ;-) > > I didn't say that it did the check at compile time, I was assuming everyone > knew that it would be done at run-time(my fault for assuming). I was coming > from the stand point of if program A called program B with 0 (zero) > parameters, but program B was expecting 1 parameter then program B would > come up with a "pointer not set for location reference" error when that > field was referenced; similar to what you are describing below but a little > different. . . >
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.