And while Barbara is implementing that feature perhaps she could add the "always" option that I've been asking for for years <grin>.

What I mean by this is a form of CONST that _always_ takes a copy and passes that. Right now it only produces a copy if there is a mismatch between the parm passed and that expected. I'd like to be able to guarantee that my data doesn't get changed no matter what happens in the called routine.


Jon Paris

www.Partner400.com
www.SystemiDeveloper.com



On Jan 13, 2010, at 5:27 PM, rpg400-l-request@xxxxxxxxxxxx wrote:

Just like the way CONST works now, the compiler generates code to
convert the data to whatever is specified on the prototype. The only
diff between this and the existing CONST support is that it'd be
roundtrip -- i.e. not just converted on input, but converted on output
as well.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.