Jon, with due deference there are a few things here I disagree with. > C functions on the other hand _only_ support passing by value. Nope. In fact strings are passed by reference by default. > When calling a C function you should always use the VALUE keyword. There's no reason to do this unless you want to protect your original values or you're passing constants from an EVAL statement. > Simple answer is _always_ pass by value then you can't get into trouble. The overhead in passing large strings into frequently used routines should alone give you reason not to do this. I do agree that the VALUE/CONST usage is more than a tad confusing (in practice rather than just in theory). I'll swear that I've got RPG routines that do similar things where VALUE will work in one and CONST in the other. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.