Variable-length fields and procedures

["Joe Teff" <jteff19@xxxxxxx>]

>From the 'ILE RPG for AS/400 Reference'

"If a subprocedure is meant to handle string data of different lengths,
using variable-length fields for parameters and return values of 
prototyped procedures can enhance both the performance and
readability of your calls and your procedures. You will not need to
pass any length parameters or use CEEDOD within your
subprocedure to get the actual length of the parameter."

Why would you not use varying length fields anytime you use
OPTIONS(*VARSIZE) for a subprocedure (other than supporting
older releases)?

Varying length fields is another one of those gems that was noted
on release documents but never really hyped. I really haven't
paid much attention to it until the recent posts on these lists.

Joe Teff

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---