|
Hi Dennis,
> I suspect that the rules that govern the operation of BIF are closely
> tied to the rules that limit our procedures' abilities.
There are existing precedents of BIFs working in an overloaded fashion.
For example, the %DEC() BIF can take a Unicode, Alphanumeric, Date, Time
or Timestamp field as it's first parameter. Indeed, the 2nd parameter
is different for a D/T/Z field than it would be if it were a character
string.
The same is true of the %date(), %char(), %int(), etc, etc BIFs... they
all can take their input from just about any data type. Something we
can't really do with subprocedures.
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.