jt wrote:
...  Frankly, I believe you don't wanna admit that /FREE, at times,
requires some pretty complex coding to do simple things, the way it is
currently designed.
Then again, you assume wrong. Sure, I'll be quite happy to admit 
that sometimes you need some complex coding to replace in /FREE what 
you could do simply in fixed calcs. But I would argue that if you're 
mixing data types (which is I think the biggest source of code 
expansion), you're probably coding your app the wrong way to begin 
with.
On the other hand, overall, there are now more ways to code things 
simpler in /FREE than in fixed calcs. For example, in keyed I/O in 
V5R2, you can list the search arguments directly instead of having 
to move them to a KLIST. And in general, you have a better chance to 
code things on one line now than before.
Cheers! Hans
 
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 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.