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



 >> There is absolutely no good reason, and no defensible rationale, for a
BIF put into free-form to not be included in RPG IV.

Sorry Joe - but I have to disagree on this one.

All of the new BIFs that can fit (e.g. %Date, %Diff, etc.) plus qualified
names and a bunch more are indeed supported in the semi-free (i.e.
EVAL/CALLP).  The only ones that are not supported are ones for which there
is a perfectly good reason not to support them other than in  /Free - the
darned things don't fir and/or have no place to put the required new
parameter (read factor).  Many of the new BIFs in V5R2 related to IO
operations don't "fit" in fixed form.  Take %Fields for example - where
exactly do you put it?

I think they did a good job of enabling the bulk of the new function in the
old format.  /Free has allowed them to expand the boundaries of the
language.

Jon Paris
Partner400
www.Partner400.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.