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



David,

One could take the approach that *all* parameter check has to be done
manually, whether or not CONST or VALUE has been specified. For instance (to
take one of my procedures I've been working on), if you have a procedure
that can accept a 3-character code, representing a record type to process
('HDR', 'DTL', OPT' etc.), then any time you call that procedure (especially
if you haven't used it for a while) you might have to check to see what the
valid record types are. Certainly a programmer who's never called that
procedure would have to do so.

In many cases, you have to know what the meanings are of different parameter
values. The same applies (or should apply) to parameter value limits.

Rory

On Fri, May 14, 2010 at 7:44 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx>wrote:

Today I learned that protoyped procedure parameter checking must be done
manually when using CONST or VALUE.
Thanks.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.